ssh_health_check

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

No annotations are present, so the description must fully disclose behavior. It only states 'comprehensive health check' without detailing what checks are performed, potential side effects (read-only assumed but not confirmed), permissions, or response format. This is insufficient for understanding the tool's impact.

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 a single concise sentence that conveys the core purpose. It is front-loaded and avoids fluff, though it might sacrifice detail for brevity.

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?

Given no output schema and no annotations, the description is too vague. It does not specify what the health check includes, how results are returned, or error handling. For a health check tool, more details on metrics (CPU, disk, memory) are expected to make it actionable for the AI.

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% with both parameters described. The parameter descriptions are clear (server name, detailed metrics). The tool description adds a high-level context but does not deepen semantic understanding beyond what the schema already provides, so baseline 3 applies.

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 'Perform comprehensive health check on remote server' clearly states the action and resource. Among siblings like ssh_connection_status and ssh_monitor, it distinguishes itself as a comprehensive health check, which is specific to this tool.

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?

No guidance on when to use this tool versus alternatives like ssh_monitor or ssh_connection_status. The description does not provide context for selection or exclusions, leaving the AI without decision support.

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