ssh_ping

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

No annotations are provided, so the description carries the full burden of disclosure, yet it only says it 'tests' connectivity and 'returns the remote identity.' It doesn't disclose what happens on failure (error? empty output?), whether it makes a network round-trip each call, how long it may block, or how the identity is formatted. For a tool that establishes or verifies a session, these behavioral details are significant gaps.

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?

At just 13 words, it is extremely concise and to the point. However, the brevity comes at the cost of behavioral transparency and usage guidance, so it's not 'zero waste' in the high-quality sense—it's simply minimal. Still, it's well-structured and front-loads the core purpose.

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 tool that tests connectivity (a side-effecting network operation with no output schema), the description is thin. Given the complexity of SSH sessions (auth, config resolution, port, identity), the description doesn't clarify error behavior, implications for session state, or how the returned identity relates to other ssh_* tools. Sibling tools like ssh_close and ssh_exec hint at session management, but this description doesn't position itself within that lifecycle.

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 has 100% description coverage for its single parameter (target = 'user@host[:port]... uses local SSH config and keys'). The description adds useful context beyond the schema by clarifying the target format and that it leverages local SSH config and keys, giving the agent enough to construct a valid value.

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 uses a specific verb+resource ('Test passwordless SSH connectivity') and identifies what it returns ('remote identity'). It clearly distinguishes itself as a connectivity test tool among siblings focused on file operations, exec, and interactive sessions. The verb 'test' makes the purpose of verification/validation clear.

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 states the core action but gives no guidance on when to use this tool versus alternatives like ssh_exec or ssh_close. It doesn't mention that it should be used to verify connectivity before attempting operations, nor does it exclude cases where password-based auth is needed. No when-not-to-use context is provided.

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