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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds useful optimistic-concurrency context ('expected revision prevents overwriting a newer edit') and durable idempotency, but it does not state failure behavior on revision mismatch or any permission/auth requirements.

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, front-loaded with the action and scope, followed by the key concurrency constraint. No sentence is padding.

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?

This is a destructive mutation with four required parameters and no output-schema explanation needed, but the description covers only one parameter's semantics and omits error/conflict behavior. For a destructive tenant-owned operation with 0% schema description coverage, this is under-specified.

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 0%, so the description must compensate. It only explains expectedRevision; it says nothing about the purpose or constraints of idempotencyKey, the format or scope of transcriptionId, or the bounds on name.

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: 'Renames one tenant-owned transcript'. Scope is clear, but there is no differentiation from nearby mutation siblings such as edit_transcript_text, move_transcript_to_folder, or rename_folder.

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?

It gives no guidance on when to use this tool versus alternatives, nor any when-not conditions. The mention of expectedRevision implies a concurrency-safety use case but does not route the agent between rename and edit operations.

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