port_status

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'Show' plus the listed metrics communicates a read-only status operation, which is useful context. However, it does not mention whether the tool errors on unknown ports, whether it is safe to call repeatedly, or what exact shape the status information takes.

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, front-loaded sentence that names the action, the target, and the three key output aspects. Every word contributes value and nothing is redundant or padded.

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?

For a one-parameter status tool with an output schema, the description covers the essential semantics: it reports on open ports and names the metric categories returned. The only notable omission is usage context, but that is already penalized under usage guidelines, and the output schema covers return details.

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 description coverage is 100%, and the lone 'port' parameter is already documented as 'A specific open port, or omit for all open ports.' The tool description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a specific verb ('Show'), a resource ('open ports'), and the meaningful details it returns (byte counters, buffered bytes, disconnect errors). It is clear enough to be distinguished from action-oriented siblings like open_port or write, but it does not explicitly contrast with list_ports, so some sibling differentiation is left to inference.

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?

No guidance is given about when to use this tool versus alternatives. An agent has to infer that this is a status/diagnostic read, and there is no mention of exclusions, prerequisites, or when list_ports or read would be more appropriate.

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