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

Goes well beyond the annotations, which only signal readOnlyHint=false and destructiveHint=false. It discloses that result download links expire after 1 hour, that the server downloads and temporarily stores the file in Cloudflare R2, processes it via a headless browser, and deletes the input when the job ends. This is exactly the lifecycle and auth/URL context an agent needs.

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-loads the purpose, then input requirement, optional parameters, return behavior, and backend lifecycle — a logical order. It is somewhat long, with the Cloudflare/headless-browser internals being borderline, but every sentence carries usable information.

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?

There is no output schema, so the description must cover return values — and it does (download links expiring after 1 hour). Combined with the input requirements and processing/storage/deletion notes, an agent has everything needed to 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 description coverage is 100%, so the schema already documents files, download_url, bitrateKbps and outputFormat. The description restates the inputs and examples ('mp3, wav, m4a') without adding syntax or constraint detail beyond the schema, matching the baseline when the schema does the heavy lifting.

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: 'Converts an audio or video file to MP3.' An agent immediately knows the operation. However, it does not distinguish itself from the numerous sibling converters (audio_converter, wav_converter, m4a_converter, ogg_converter, video_to_audio), and its mention that outputFormat may be 'wav, m4a' actually blurs the boundary further.

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 supplies an input prerequisite ('one file with a public HTTPS download_url') but never states when to choose this tool over the near-identical sibling converters, nor any when-not conditions. Usage is only implied by the tool's purpose.

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