hostodo_create_snapshot

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

Despite no annotations, the description fully discloses the tool's stub behavior: it returns a structured 'coming_soon' response and does not execute the snapshot creation. It also warns about not sending secrets, which is critical for safe usage.

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 short sentences that efficiently convey purpose, behavior, and a critical warning. No unnecessary words, and the most important information (stub nature) is front-loaded.

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 that this is a stub tool with no output schema, the description sufficiently explains the behavior (records demand, returns coming_soon response). It covers the tool's limitations and safety concerns, making it complete for its intended use.

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 input schema already describes all 4 parameters (100% coverage), but the description adds important semantic context: parameters are optional, metadata is for PMF discovery, and secrets should not be included. This aids proper usage beyond the 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 starts with 'Create a VM snapshot' which clearly states the intended action, but immediately clarifies that this is a PMF stub that only records demand and does not perform the action. This provides an accurate understanding of the tool's actual purpose, though the initial phrase could be misleading if not read in full.

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 states when to use this tool (to record demand for a future snapshot feature) and provides a strong negative guidance: 'Do not send secrets.' It also explains that it does not perform the requested action, helping the agent avoid incorrect expectations.

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