hostodo_restore_snapshot

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

With no annotations, the description carries full transparency burden. It honestly discloses the tool does not perform the action, only returns a structured stub response. The warning about not sending secrets adds cautionary behavior.

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?

Two short, front-loaded sentences. Every sentence adds value: one explains the stub nature, the other warns about secrets. No extraneous text.

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 conveys it is not functional and records demand. It mentions the structured 'coming_soon' response. Could slightly improve by describing response fields, but overall adequate given tool's limited 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 coverage is 100% with parameter descriptions, so baseline is 3. The description adds no additional parameter meaning beyond 'do not send secrets', which is a general caution rather than parameter-specific semantics.

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 tool is a stub that records demand for restoring a snapshot, not an actual restoration. It distinguishes from siblings like hostodo_create_snapshot which performs a real action. The purpose is specific: logging interest for a future feature.

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 lacks when-to-use guidance. It only warns 'Do not send secrets' and states it returns a 'coming_soon' response. There is no comparison to alternatives or context for when this stub is appropriate versus real tools.

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