Get all SSH hosts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the 'authenticated user' scope, which is useful but minor. It does not contradict annotations and does not add significant behavioral detail beyond that.

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 two short sentences with no repetition or filler. The core action and scope are front-loaded. Every word earns its place; it is appropriately concise for a simple list operation.

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 get-all list tool with no parameters and annotations covering safety, the description is nearly complete. It does not specify the return format (e.g., host IDs, names, details) which could be helpful, but given the simplicity and absence of an output schema, it is adequate overall.

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?

There are zero parameters and schema coverage is 100% (vacuous). No parameter explanations are needed. The baseline for 0 params is 4, and the description adds nothing that could improve parameter semantics since there are none to explain.

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 'Retrieves' and the resource 'all SSH hosts' plus the scope 'for the authenticated user'. It distinguishes from sibling tools like get_ssh_host_id by the explicit 'all' scope, so an agent can immediately understand it lists everything rather than a specific host.

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 implies usage (use when you need all SSH hosts) but provides no explicit alternatives or exclusions. It does not mention that for a specific host you should use a different tool, nor does it contrast with filters. This is adequate but not fully explicit.

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