hostodo_list_ssh_keys

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

The description fully discloses its stub behavior: it 'returns a structured coming_soon response' and warns 'Do not send secrets.' This is highly transparent despite the lack of annotations, leaving no ambiguity about side effects or safety.

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 three sentences, front-loaded with the key purpose ('Coming soon (access): List SSH keys'), and every sentence serves a clear purpose: stating nature, behavior, and security warning. No unnecessary words.

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 tool is a stub with no output schema, the description is fully complete: it explains what it does (records demand), what it returns (coming_soon response), and a critical security note. No additional information is needed for an agent to use it correctly.

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?

Schema coverage is 100%, and the description adds no further parameter semantics beyond the schema definitions. The 'Do not send secrets' warning is generic and not parameter-specific, so the description meets the baseline but does not enhance parameter understanding.

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 states it is 'a PMF stub that records demand' and 'does not perform the requested action yet,' clearly indicating it is a placeholder for listing SSH keys. This distinguishes it from sibling tools like hostodo_add_ssh_key and hostodo_remove_ssh_key, but the 'Coming soon' phrasing slightly impairs clarity about its real behavior.

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 explicitly says it does not perform the action and records demand, implying it should be used only to gauge interest. However, it does not mention alternatives or when to use actual list functionality, leaving unclear guidance for agents expecting real SSH key listing.

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