Generate Estimate Cost

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

The description adds the useful context that this is a pre-creation cost estimate and that it shares the request body with generate_create-generation. However, it does not disclose whether the tool has any side effects (e.g., consumes credits, logs calls) or address the readOnlyHint=false annotation, leaving some ambiguity. No direct contradiction with 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 two sentences long, front-loaded with the core action, and contains no filler. Every word earns its place.

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?

The description conveys the essential purpose and relationship to another tool, but lacks details on the output format (cost estimate structure), parameter semantics, and any usage constraints. Given the absence of an output schema and parameter descriptions, more context would be needed for full self-sufficiency.

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?

With 0% schema coverage, the description partially compensates by stating 'Takes the same body as generate_create-generation,' which points to another tool for parameter meaning. However, it does not directly explain the parameters (e.g., fps, duration, reasoningEnabled), leaving the agent to cross-reference.

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's purpose with a specific verb ('Estimate') and resource ('credit cost of a generation'), and explicitly distinguishes it from generation creation by noting 'before creating it.' This differentiates it well from sibling tools like generate_create-generation.

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 provides clear context for when to use this tool ('before creating it') and references generate_create-generation, indicating it is a pre-flight check with the same request body. It does not explicitly state when not to use it, but the implied usage is clear.

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