AI Generate

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

Annotations only declare it is a non-idempotent, open-world write; the description adds the economically critical behaviors: it SPENDS credits, requires a prior price check and user consent, and that provider-failed, blocked or cancelled jobs refund credits. That is substantive context not derivable from the annotations or schema.

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?

Three dense sentences with zero filler, front-loaded with the action and the credit-spend warning before the follow-up tool chain. Nothing is repeated from the title or schema.

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 an 11-parameter, nested-object, no-output-schema tool this covers the essentials: what it returns (generation ids), the required workflow, and the credit risk. It stops short of clarifying required-vs-optional parameter combinations or the recipe/model exclusivity in prose, which the agent must infer from the schema.

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 91%, so parameter meaning is already largely documented (refs kinds, model/recipe distinction, expectedCredits refusal, ownFootage/productAuthorized consent flags). The description adds no parameter-level syntax or format detail beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ('Start an AI image or video generation') and immediately distinguishes it from the sibling tools that handle its lifecycle (ai_price, ai_status, ai_download, ai_cancel). An agent can identify the tool's role without opening the schema.

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?

Gives explicit sequencing: price with ai_price, get the user's OK first, then follow ids with ai_status and save with ai_download. It names the alternatives and the conditions that select them, which is exactly the routing an agent needs.

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