send_custom_command_parallel

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

No annotations are provided, so the description should fully disclose behavioral traits. It mentions parallel execution but lacks details on failure handling, parallelism limits, authentication requirements, idempotency, or safety implications. The description is too shallow for a tool that executes arbitrary commands.

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?

The description is concise: two short paragraphs plus an example. The warning and parameter info are front-loaded, and every sentence adds value. No extraneous text.

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 parallel SSH command tool with 2 parameters and no output schema, the description covers the input format and usage guidance but omits return value structure, error behavior, and the timeout default inconsistency leaves a gap. It is mostly complete but has notable missing context.

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?

With 0% schema description coverage, the description must compensate. It explains the targets format (list of dicts with ip and command) and timeout with default. However, there is a contradiction: description states timeout default is 30s, but the schema specifies 120. This inconsistency reduces reliability.

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 multiple generic network devices in parallel, using specific verbs and resources. It explicitly excludes Palo Alto firewalls and names the alternative tool, distinguishing it from siblings.

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 when to use (generic devices) and when not to use (Palo Alto), directly referencing the alternative tool 'paloalto_send_command_parallel'. This provides clear usage context and exclusion criteria.

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