transcribe_url

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

With no annotations, the description carries the full burden. It discloses the three-tier strategy (subtitles, Whisper, closed-platform guidance) and sync/async behavior. It doesn't cover error handling or permissions, but the tier strategy provides substantial behavioral insight.

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?

The description is front-loaded with the main purpose, structured into clear tiers, and every sentence contributes actionable information without redundancy. It is concise yet comprehensive.

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?

Given 7 parameters, no output schema, and no annotations, the description covers the workflow well: tiers, sync/async, polling, and closed-platform guidance. It could explicitly state the sync return value, but the tier strategy and usage notes make it largely complete.

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 baseline is 3. The description adds value by explaining async_mode for long videos, segment_minutes for 1h+, and sync mode default, enriching the schema's parameter descriptions.

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 states a specific verb and resource: 'Transcribe a video from URL using three-tier strategy.' It clearly distinguishes from siblings by mentioning polling with get_transcript_status and contrasting with transcribe_file (via the URL versus file input).

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?

Explicit guidance is given: 'For videos under 30 minutes, use sync mode (default)... For longer videos, set async_mode=true... poll with get_transcript_status.' It also advises adjusting segment_minutes for 1h+ videos, clearly indicating when to use which mode.

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