listKnownHosts

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: the consolidation of multiple sources, prioritization logic, and the specific file paths involved. It doesn't mention potential issues like file permissions, missing files, or output format details, but provides solid operational context.

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, well-structured sentence that efficiently conveys the tool's purpose, data sources, and prioritization logic. Every element earns its place with no wasted words, making it easy to parse and understand.

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 zero-parameter tool with no annotations or output schema, the description provides strong context about what the tool does and how it operates. It could be more complete by mentioning the return format or handling of edge cases, but it adequately covers the core functionality given the simplicity.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters, focusing instead on the tool's behavior and data sources, which adds value beyond the empty schema.

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 specific action ('Returns a consolidated list') and resource ('all known SSH hosts'), with explicit prioritization rules (~/.ssh/config entries first, then ~/.ssh/known_hosts). It distinguishes itself from sibling tools like 'getHostInfo' by focusing on listing rather than detailed information retrieval.

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 context through the prioritization rules, suggesting it's for retrieving SSH host configurations. However, it lacks explicit guidance on when to use this tool versus alternatives like 'getHostInfo' or 'checkConnectivity', and doesn't mention prerequisites or exclusions.

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