port_overview

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

With no annotations, the description carries the full burden and does well: it declares read-only, that only hardcoded show commands are executed, that they pass through the same command filter as the show tool, and that it never sends config. It omits latency/timeout characteristics of running a bundle of commands and any failure behavior.

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?

Front-loaded with the action, then a separate safety paragraph; two short sentences that earn their place. Slight overlap between 'Read-only' and 'Never sends config,' though the latter adds concreteness.

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?

An output schema exists, so return values need not be described, and there are no parameters to explain. The remaining gap is that the description never says which status commands are bundled or how the target session is established, which an agent may want to know before calling.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The absence of a device/target parameter is only implicitly explained by 'in a single session.'

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?

States a specific verb and scope: 'Read a bundle of allow-listed status commands in a single session,' which distinguishes it from the single-command 'show' sibling by batching. It stops short of naming what status is actually surfaced (port state, counters, etc.), so the resource is somewhat abstract.

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?

'In a single session' implies the tool is the batch-efficient alternative to issuing several show commands, but there is no explicit when-to-use or when-not-to-use guidance and no sibling is named for routing. The reference to 'the show tool' is about filtering mechanics, not about which tool to pick.

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