read_ssh_pool_status

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

With no annotations provided, the description bears the full burden of disclosure. It only states that the tool gets status/health, implying a read-only operation, but does not elaborate on any behavioral traits such as authentication requirements, rate limits, or side effects. No destructive or idempotent hints are given.

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 sentence with no wasted words. The category tag '[SSH Operations]' provides useful context. It is concise and effectively front-loaded with the action and resource.

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 the lack of output schema and annotations, the description is incomplete. It does not specify what format or fields the status/health output contains (e.g., JSON, connection counts, error states). For a tool that returns status, this omission limits an agent's ability to interpret results.

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 tool has zero parameters, and schema description coverage is 100% by default. The description does not need to add parameter information since none exist. This meets the baseline for parameter semantics with no parameters.

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 'Get' and clearly identifies the resource as 'status and health of the SSH connection pool'. It distinguishes this tool from sibling tools like 'create_ssh_connection' or 'test_connection' by focusing on pool-level health rather than individual connections or commands.

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 provides no guidance on when to use this tool versus alternatives such as 'test_connection' or 'read_ssh_connections'. It does not mention prerequisites, exclusions, or typical scenarios, leaving the agent to infer usage without any comparative context.

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