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

Goes well beyond the annotations by disclosing the full lifecycle: the server downloads the file, stages it in Cloudflare R2 for the job duration, processes it via a headless browser, deletes the input when the job ends, and issues download links that expire after 1 hour. This is exactly the kind of operational context annotations do not carry.

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, followed by input constraints, settings, output, and lifecycle. Most sentences earn their place, though the Cloudflare/headless-browser implementation detail is more verbose than an agent strictly needs.

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 mutation tool with no output schema, the description supplies the input contract, return artifact (download links), expiry, and cleanup behavior, so an agent has what it needs to call it. The loose 'settings' sub-parameters remain under-specified.

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 schema already documents files, download_url, bitrateKbps, and outputFormat; the settings object itself is an untyped additionalProperties bag. The description adds only the raw setting names (amountDb, cornerHz, keepLevel) with no ranges, defaults, or meaning, so the baseline 3 is appropriate.

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?

Names a specific verb and resource ('Boosts the low frequencies'), which is clearly distinct from siblings like volume_booster by targeting the low end specifically. However, it never explicitly contrasts itself with volume_booster or equalizer, leaving the agent to infer the boundary.

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 operability (input must be a public HTTPS download_url) but gives no when-to-use guidance and never names alternatives such as volume_booster or equalizer for overlapping requests. An agent must guess which sibling to pick.

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