ssh_test_all_connections

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

No annotations provided; description only states it tests connections and reports status. Lacks details on whether it's destructive, timeout behavior, or format of status report (aggregate vs per-server).

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?

Single sentence with verb first ('Test'), no redundancy, perfectly sized for the simple tool.

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?

Adequate for a straightforward test tool with one parameter. Could benefit from describing the output format, but not critical given the action is clear.

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 covers the single parameter 'parallel' (100% coverage). Description adds context that parallel is 'faster', providing marginal extra meaning beyond the schema's 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?

Clearly states it tests connections to all configured servers and reports status. Distinguishes from sibling ssh_test_connection (single server) and ssh_connect (establish session).

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?

Implied use for bulk testing but no explicit guidance on when to use vs alternatives (e.g., ssh_test_connection for testing a single server) or when not to use.

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