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

Annotations only flag the operation as non-read-only, non-idempotent and non-destructive; the description adds substantial behavioral context beyond that. It discloses the download-link expiry (1 hour), the R2 staging lifecycle, the headless-browser processing path, and crucially that the input is deleted when the job ends.

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?

Purpose is front-loaded in the first sentence and the parameter/return details follow in a logical order. The Cloudflare R2 and headless-browser infrastructure sentences are slightly verbose but do serve the transparency goal, so little is wasted.

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 carries the return-value burden and does so by stating that download links are returned and expire after an hour. Combined with input and lifecycle details, the definition is nearly complete, missing only explicit alternative-tool routing.

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%, so the baseline is 3, but the description adds real value: the 'settings' object in the schema is an open object with no defined properties, and the description tells the agent the key to place inside it (sampleRateHz). It also clarifies that outputFormat/bitrateKbps only apply 'where the tool supports them'.

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 ('Resamples audio to a different sample rate'), which cleanly separates it from the format-conversion siblings like mp3_converter or audio_converter. It never names those siblings explicitly, so an agent gets a clear purpose but no in-text routing cue.

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 gives input requirements ('one file with a public HTTPS download_url') but no when-to-use vs when-not guidance and no mention of alternatives such as speed_changer or the format converters. The agent must infer the selection context entirely.

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