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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: charging rules (invalid input and all-fail calls are never charged), robots.txt compliance, the User-Agent string, and refusal of private/internal addresses. This is unusually rich behavioral disclosure.

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?

Front-loaded with limits, format support and the payment gate, and every clause carries information. Some sentences run long and pack multiple ideas, but nothing is pure filler.

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 a paid, open-world fetch-and-transcribe tool with no output schema, the description covers inputs, cost, error/payment protocol, and safety constraints in enough depth that an agent can invoke it correctly.

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 coverage is 100% and the description largely echoes the schema (formats, language, task=translate, payment location). It adds only marginal value, such as emphasizing the payload is never a private key, 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 (transcribe one short audio file) plus the backing model, supported formats, size/duration limits, and the second mode (translate to English). No sibling tool does transcription, so the scope is unambiguous.

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?

Explicitly excludes YouTube and social media pages, states 'Paid only' with the price, and spells out the failure path (isError + PaymentRequired object) and the retry condition. An agent knows exactly when this tool applies and how to proceed after a payment failure.

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