cisco_backup

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

With no annotations, the description carries the full burden and does so well: it discloses that Telnet sessions auto-send 'terminal length 0', that SSH sessions do not because each command runs in an ephemeral session, and that SSH pagination can silently truncate output to the first page. It omits auth requirements and does not restate the read-only nature, but the pagination/transport behavior is genuinely valuable context beyond the schema.

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?

Purpose is front-loaded in the first clause, with transport caveats following. The nested em-dash parenthetical is dense but each clause earns its place by preventing a wrong conclusion about output completeness.

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-value explanation is not required, and the description supplies the one non-obvious operational risk (SSH truncation). For a single-parameter fetch tool this is close to complete; only credential/prerequisite context is absent.

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?

Only one parameter exists and schema description coverage is 100% ('the inventory router/switch name'), so the schema already does the work. The description adds no syntax, naming convention, or validation detail about the device argument. Baseline 3 is appropriate.

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 resource ('Fetch a Cisco device's running configuration') and even names the underlying command ('show running-config') plus the 'as-is' scope. It does not, however, distinguish itself from the sibling cisco_backup_diff, which is the obvious adjacent tool an agent might confuse it with.

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 explains condition-dependent behavior (Telnet vs SSH) and a truncation caveat, which implies when the output will be complete. But it never states when to choose this tool over cisco_backup_diff or any other sibling, and gives no prerequisites such as credential or reachability requirements.

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