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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, but the description adds substantial behavioral context: the probe originates from netmon rather than mcpmond, latency is ~30-90s with a 120s client timeout, and the precise return structure (host element with status, address, ports[]). It also mentions the permission requirement ('tools'). This goes well beyond the 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 front-loaded with the core purpose in the first sentence, then builds logically: wrapping endpoint, origin, constraints, return format, latency, and an example. Every sentence contributes new information; no filler or repetition. The structure is easy to parse and the example at the end aids comprehension.

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?

Despite lacking an output schema, the description fully specifies the return format (nmap host element as JSON with status, address, ports[].state/service/product/version). It also covers latency, timeout, permissions, and the single-target constraint. For an agent to call this tool correctly, nothing essential is omitted.

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?

Schema coverage is 100% for both parameters, and the schema already documents both fields including the CIDR limitation and default. The description adds value by providing a concrete example, reiterating the default range behavior, and clarifying the exact serialization of port_range. This enhances the schema rather than merely repeating it.

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 states a specific verb+resource: 'Nmap port scan against a single host from the Netmon server.' It names the wrapped endpoint (POST /api/getPortscanInfo) and clarifies the scope (single IP/hostname only). This clearly distinguishes it from sibling network tools like ping, traceroute, or arp_lookup without ambiguity.

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 clearly indicates when to use the tool: for port scanning a single host from Netmon's perspective, and it explicitly states the constraint that CIDR or ranges are not accepted. However, it does not explicitly name alternative tools or conditions when another tool would be preferred, leaving the 'when-not-to-use' guidance implicit rather than direct.

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