transcription_set_model

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

No annotations provided, so description carries full burden. Discloses [EXPERIMENTAL] status, background execution ('returns a job_id immediately'), prerequisite setup requirements, and references monitoring mechanism. No contradictions with annotations (none exist).

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?

Information-dense and well-structured with logical flow: experimental warning → usage constraints → prerequisites → execution model → monitoring → parameter details. Every sentence provides actionable guidance, though the model size enumeration adds length it is justified by the need to explain trade-offs.

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?

Comprehensive coverage for a background job tool with no output schema: explains return value (job_id), asynchronous nature, prerequisite setup, monitoring workflow via sibling tool, and parameter selection criteria. No gaps remain for agent operation.

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 has 0% description coverage (no 'description' field in properties). Description fully compensates by listing valid values ('tiny', 'base', 'small', 'medium', 'large-v3') and providing detailed size/accuracy trade-offs for each option (~75MB to ~3GB with performance characteristics).

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?

Description clearly states 'Pre-download a whisper model' with specific verb and resource. Explicitly distinguishes from sibling transcribe_audio by stating transcription tools 'handle model loading automatically' and this should only be called for explicit download requests.

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?

Provides explicit when-to-use ('ONLY call this if the user explicitly asks to download or change the model') and when-not-to-use ('Do NOT call this before transcribe_audio'). Names the specific sibling tool (check_transcription_status) for monitoring progress.

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