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

The description adds lifecycle behavior: deprecation, backward-compatibility scope, and removal version. However, it delegates all runtime behavior to transcribe_url and does not disclose side effects, return behavior, or async characteristics beyond what the schema hints at.

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 a single compact sentence that leads with the deprecation warning and alternative before explaining compatibility and removal. Every clause earns its place with no redundancy.

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 deprecated alias, pointing to transcribe_url and covering all parameters via schema is largely sufficient. Still, with no output schema and no mention of return values or event behavior, an agent encountering this tool alone would need to inspect transcribe_url for complete operational context.

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 parameters are already fully documented. The description adds no parameter-level semantics, which is acceptable but not helpful beyond the baseline.

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 immediately identifies the tool as a deprecated alias for transcribe_url and states 'Identical behavior to transcribe_url', which establishes the action and resource by reference. The annotation title 'Transcribe from URL' adds basic purpose, though actual behavior is not independently described.

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 explicitly says to use transcribe_url instead, marks the tool as deprecated, and states removal plans. This is unambiguous when-to-use versus when-not-to-use guidance, with the alternative named directly.

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