validate_ssh_connection

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'validate configuration and test connectivity' but fails to specify whether an actual connection is made, what constitutes success/failure, or any side effects. The behavior is vague.

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 very short and to the point, using a single sentence plus a category prefix. It is efficient with no wasted words, though it could benefit from slightly more structure.

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 annotations, no output schema, and a complex nested parameter, the description is incomplete. It does not explain return values, error handling, or whether 'test connectivity' implies a real connection attempt. The tool's behavior is underspecified.

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?

The schema description coverage is reported as 0% for the top-level parameter, though nested properties have descriptions. The description does not add meaning to the 'connectionConfig' parameter beyond what is in the nested schema. It does not compensate for the missing top-level parameter 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?

The description clearly states the verb 'validate' and the resource 'SSH connection configuration', and includes a category prefix '[SSH Operations]'. It distinguishes from sibling tools like 'create_ssh_connection' or 'delete_ssh_connection' by focusing on validation and connectivity testing.

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 does not provide any guidance on when to use this tool versus alternatives such as 'check_security_config' or 'create_ssh_connection'. It lacks explicit context for selecting this tool over siblings.

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