get_price

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

Annotations already declare readOnlyHint, and the description adds useful behavioral details: the tool is 'Free', returns an 'exact cost', and its output depends on optional input like video duration or TTS character count. This enriches the safety profile without contradicting 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 with no wasted words. It front-loads the core purpose and immediately follows with the key nuance about input-dependent pricing and the 'Free' attribute.

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 simplicity, an output schema exists, and parameters are well-described, the description covers the essential context: cost per call, optional input effects, and no charge. It doesn't explain edge cases like invalid model IDs, but that's not critical for this straightforward tool.

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?

Though schema coverage is 100%, the description adds valuable examples for the 'input' parameter (e.g., duration, text) and clarifies that the model id comes from list_models. This helps the agent understand how to construct pricing queries beyond the schema alone.

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 function: 'Quote the exact cost of one call for a model' with a specific verb and resource. It also distinguishes itself from sibling tools like list_models or generate by focusing on pricing, including optional input that affects cost.

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 on when to use the tool: to get pricing for a single call, optionally with input that affects price. It doesn't explicitly name alternatives or exclusions, but the context implies it's the pricing companion to generate and list_models.

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