generate

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

Beyond annotations (readOnlyHint=false), the description discloses the paid nature ('settles the price from your wallet'), output types (media URL vs assistant text), and file upload constraints. It adds significant behavioral context without contradicting the 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 somewhat long but every sentence carries useful information. It is front-loaded with the main purpose, then precision details. The structure flows logically from general to specific, with no redundancy.

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, the description covers all critical aspects: output formats, input variations, payment side-effects, prerequisites, and file handling. An output schema exists, so return values are not required, and the description does not omit essential operational details.

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?

Despite high schema coverage, the description substantially enriches parameter understanding: it explains OpenAI-style input for text models, the requirement of public URLs for file fields, and the array format for multi-reference images. This goes well beyond the bare schema descriptions.

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 opens with 'Run a model and return the result', clearly stating the core function with a specific verb and resource. It distinguishes between media and text model outputs, and contrasts with sibling tools like get_schema and get_price by identifying generate as the execution step.

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 usage context, instructing to call get_schema first and get_price for cost, and explaining how to handle file inputs (public URL, upload limit). It doesn't explicitly state when not to use the tool, but the referenced sibling tools make the distinction obvious.

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