send_command

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

With no annotations, the description carries the full burden. It discloses that the tool waits for the prompt and automatically handles pagination, which is useful. However, it does not mention what the tool returns (e.g., command output), whether an open connection is required, or error/timeout behavior, leaving significant behavioral gaps.

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?

Two sentences, no redundant words. The first sentence delivers the core purpose, the second adds a key behavioral trait. Every word earns its place, making it highly concise and well-structured.

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?

The tool has no output schema, so the description must explain return values, but it does not. It also omits prerequisites (e.g., an open port via open_port) and failure modes. While the description covers the happy path and pagination, it is insufficient for an agent to fully understand the tool's context within the serial-port workflow.

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%, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema; it doesn't mention path, command, or timeout. The schema already documents these accurately, so no deduction is warranted, but no additional value is provided either.

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 clearly states the action ('Send a command') and target ('to a Cisco device'), with specific behavior ('wait for the prompt', 'Handles -- More -- pagination automatically'). This distinguishes it from siblings like write_raw (raw bytes) and read_buffer (reading data), making the tool's purpose unambiguous.

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 implies usage for command-line interaction with Cisco devices, but does not explicitly state when to use it over alternatives like write_raw or read_buffer. No exclusions or alternative tool references are provided, so the guidance is only implicit.

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