plan_rental

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

Annotations indicate readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds that it stores a signed plan, which is non-destructive but not read-only. It does not explain the lifecycle of the stored plan or return format, though an output schema exists. Moderate additional context beyond annotations.

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 concise sentence that is front-loaded with the core action. However, it sacrifices detail for brevity, making it less informative than it could be. Every word earns its place, but the balance is slightly off.

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's complexity (10 parameters, 0% schema coverage, multiple siblings, and an output schema), the description is insufficient. It does not explain the output (signed plan), how parameters interact, or how it relates to siblings like 'catalog' or 'rent'. The agent would need additional knowledge 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 description coverage is 0% for 10 parameters. The description does not explain any parameter semantics beyond the schema's titles and defaults. It fails to compensate for the lack of parameter documentation, leaving the agent without guidance on how to set values like 'kind', 'min_cpu', 'gpu_type', etc.

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 it selects and quotes compute, storing a private signed plan, and explicitly notes 'never creates,' which distinguishes it from sibling tools like 'rent' and 'release'. The verb+resource pair 'Select and quote compute' is specific.

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 for obtaining a quote before renting ('never creates'), but does not explicitly mention when to use versus alternatives like 'catalog' (for listing options) or 'rent' (for actual rental). No when-not-to-use guidance is provided.

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