IT Tools MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint=false, indicating this is a mutation tool (generates new data), which aligns with 'Generate'. The description adds no behavioral details beyond this, such as whether ports are guaranteed unique, if there are rate limits, or what the output format is. With annotations covering the mutation aspect, a baseline 3 is appropriate as the description doesn't add significant context but doesn't contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient phrase ('Generate random port numbers') that is front-loaded and wastes no words. It directly conveys the core function without unnecessary elaboration, making it highly concise and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (generation with parameters) and lack of output schema, the description is minimal but adequate with annotations. It covers the basic purpose but lacks details on output format or usage context. With annotations providing some behavioral hints, it meets a minimum viable level but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear parameter descriptions (e.g., 'Number of ports to generate' for count). The tool description adds no additional parameter semantics beyond what the schema provides, such as default ranges or constraints. With high schema coverage, the baseline is 3 as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Generate random port numbers' clearly states the verb ('Generate') and resource ('random port numbers'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'lookup_port_numbers' or 'calculate_ip_subnet', which serve different purposes but involve ports/networking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this generation tool is appropriate compared to lookup tools (e.g., 'lookup_port_numbers' for known ports) or other calculation tools in the sibling list, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.