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

Annotations only supply generic hints (readOnlyHint=false, idempotentHint=false), so the description carries the real burden and does it well: it discloses that the call is PAID, the exact pricing formula, that metering retains token counts only, the auth header forms accepted, and the failure payload when no key is present. These are behaviors an agent cannot infer from the annotation block or the 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?

Information-dense and front-loaded — capability, then payment precondition, then pricing — with no filler sentences. The heavy em-dash parentheticals make it slightly cramped to parse, but every clause carries load-bearing content.

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?

With no output schema, the description supplies the return shape ({choices, usage}) and the alternate payment-requirements response, plus the auth and billing model. Given four fully documented parameters and no nested objects, nothing an agent needs to call this correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning by tying maxTokens directly to billing ('Price = ... max_tokens × output rate — set max_tokens tight to bill tight'), which the schema does not state. The model parameter is only cross-referenced to textModels rather than explained further.

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 operation and resource — 'OpenAI-compatible chat completions' over frontier and open-weight models — and tells the agent where the model list lives. This separates it cleanly from generate_image and the prompt/reference tools in the sibling set.

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 explains the two execution paths (key present → runs; key absent → 402 + x402 requirements) and advises setting max_tokens tight, which is genuine usage context. However, it never routes the agent to siblings such as quote_price for a cost preview, recommend_model for model choice, or list_models for enumeration, and gives no when-not-to-use condition.

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