hostodo_list_snapshots

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

The description fully discloses that the tool is a stub and does not perform the intended action. This is a high level of transparency, especially with no annotations to fall back on.

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 sentences plus a warning, all essential. It is front-loaded with the key 'Coming soon' nature, then provides critical details. No extraneous information.

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 stub tool, the description adequately explains what it does and what it doesn't do. It could mention the return format more explicitly, but it is sufficient for its purpose.

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 description coverage is 100%, so baseline is 3. The description does not add any extra meaning beyond what the schema already provides for the 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 explicitly states it is a 'PMF stub' that 'records demand' and does not perform the requested action. It clearly defines what the tool does (list snapshots is aspirational) versus its actual behavior (recording interest).

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 warns 'Do not send secrets' and implies it is for demand recording, but does not explicitly say when to use this tool versus alternatives (e.g., if actual snapshot listing is needed). The context is clear but not complete.

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