set_language

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

No annotations are provided, so the description bears full responsibility. It discloses that the change occurs over WebSocket without app restart and applies on the next recording. This provides good insight into the tool's behavior, though it does not discuss potential permissions or side effects.

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?

Two sentences: the first clearly states the purpose and examples, the second provides behavioral details. No extraneous information, every sentence contributes.

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 one-parameter tool with no output schema, the description fully explains what it does, how it works (hot-swappable), and when changes apply. Complete and sufficient.

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% with the description 'ISO 639-1 code or "auto".' The tool description adds value by listing common examples and noting hot-swappability, which helps the agent understand the parameter's context beyond the schema.

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 tool's purpose is explicitly stated: 'Set the Whisper transcription language.' It specifies the verb (Set), the resource (Whisper transcription language), and provides a clear list of example ISO codes and 'auto'. This distinguishes it from any potential sibling tools (none directly related to language setting).

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 mentions that this mirrors a specific settings location ('Settings → Transcription → Language') and states that it is 'hot-swappable' and applies on the next recording. However, it does not explicitly exclude scenarios or provide alternatives, but given no sibling tool for language, this is sufficient.

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