There is a free ports tool up on ZipForge but it uses SNMP as it has lower overhead. Would this be suitable?

Our management would like a better understanding about which ports are used and which ports are not used in the network. The Free Ports tool does address part of this request, but we would like the tool to go a step further by including information about used ports and/or function. Many locations typically have more ports than there are staff with PCs. The network team provisions ports for many reasons; such as Laptops, PCs, Printers, Servers, IP attached Storage, IP attached Mainframe, IP FAX, IP Telephony Handsets, IP PBX Cards, Wireless Access Points, and/or general network connectivity (switch to switch, or router to switch, etc). The ability to create a report that explains or summarizes how or why ports relate to different functions or locations would better answer management's request. We believe this could be done by using the Free Ports Tool concept and standard port descriptions and/or diagnostics or telemtry data from network devices. The Free Ports Tool addresses the free versus used port question, and standard port descriptions and/or diagnostic data could answer how/why/what questions regarding port use. The resulting report could be expanded upon further by correlating port counts with known port costs to answer questions about Total Cost of Ownership (TCO) and/or Return On Investment (ROI) for port provisioning in general. This is something that would be useful during build out and budget exercises. I welcome feedback and/or suggestions for how to best approach this challenge. We are by no means Perl experts, but would be interested in such a tool as described above. Thanks much!