Send CLI Command to a Cisco Device

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

Annotations only flag readOnlyHint=false / destructiveHint=true; the description goes well beyond by stating it works before boot completes, that sub-modes carry over between commands, and that status can be 'invalid'/'incomplete'/'ambiguous' when IOS rejects input. The CRITICAL state-mutation warning reinforces the destructive annotation rather than contradicting it.

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 purpose sentence, then tight bullets for the multi-command and mode rules, a bolded safety warning, and short natural-language examples. Every line maps to a decision the caller has to make; there is no filler.

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?

Output schema and annotations already cover return shape and destructiveness, and the description handles the mode semantics thoroughly. It is silent on failure handling for an unknown or powered-off device name and on any confirmation/rollback behavior, which are the remaining gaps for a destructive tool.

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 only 33% (commands and config_command are bare), and the description fully compensates: newline separation for multiple commands, the default and meaning of config_command, sub-mode persistence, and the exact command prefix to omit. Only 'name' relies on the schema, and that carries a description.

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?

A specific verb+resource pair — 'send IOS commands to a Cisco device... and return each command's status and output' — with the supported device families enumerated. It never distinguishes itself from the neighboring send_terminal_command or configure_device tools, so an agent must guess which of the three to pick.

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 two operating modes are spelled out with concrete guidance: config_command=false targets privileged exec, config_command=true targets configuration mode with an explicit 'DO NOT include enable/configure terminal/end'. There is clear context but no exclusion rules relative to sibling tools that also push commands to devices.

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