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

Annotations already mark readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false; the description adds beyond these by disclosing an auth requirement ('Requires a configured API key') and a known failure mode of auto-detection. It does not contradict annotations, and the added context helps agents anticipate edge cases even though side effects like cost are not mentioned.

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?

Four sentences, each earning its place: purpose, capabilities, parameter recommendation with rationale, and prerequisite. The recommendation is front-loaded in a clearly highlighted RECOMMENDED block, and there is no filler or repetition of schema 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?

The description conveys the core operation and a key usage caveat, but with no output schema it omits the return value and the async/polling behavior implied by await_completed and webhook_url. It also does not mention that transcription can be long-running or that webhook events will be delivered. This leaves an agent partially uninformed about what to expect after calling the tool.

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%, establishing a baseline of 3. The description adds value beyond the schema by recommending the language parameter explicitly and explaining the failure conditions that justify it. It also ties top-level features (diarization, word-level timestamps) to the relevant parameters, giving agents extra semantic anchoring.

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?

The description opens with a specific verb and resource: 'Transcribe audio or video from a public URL using Scriptivox AI.' This clearly distinguishes it from sibling transcribe_upload (local file upload) and transcription_url (URL retrieval) by emphasizing the public-URL input. The feature summary (119 languages, diarization, timestamps) reinforces scope.

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 concrete guidance on when to pass the language parameter explicitly, noting auto-detect failure on short clips, code-switched audio, and music-leading files. It also states the API key requirement. It does not explicitly contrast with alternatives (e.g., when to prefer transcribe_upload), but the public-URL wording and parameter guidance supply clear usable context.

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