send_custom_command

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

No annotations provided, so description must cover behavioral traits. It discloses that the tool works with standard SSH devices and not PTY sessions, but lacks details on authentication, possible destructive actions, rate limits, or output format. Adequate but minimal.

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 concise sentences plus a warning; no fluff. Front-loaded with purpose and key exclusions.

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 generic SSH command tool with no output schema or annotations, the description covers scope and exclusions but omits prerequisites, authentication, and expected return values. Adequate but not comprehensive.

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 has 0% description coverage. Description does not explain 'identifier' (likely device ID) and only implies 'command' is the SSH command. Users must infer meaning from context, reducing clarity.

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 tool executes SSH commands on generic network devices (Cisco, Juniper, Arista, Linux) and explicitly excludes Palo Alto firewalls, distinguishing it from sibling tools like paloalto_send_command.

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?

Description provides explicit when-not-to-use guidance (not for Palo Alto) and directs to an alternative (paloalto_send_command). It also specifies suitability for standard SSH devices without PTY interactive sessions.

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