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

Annotations already declare destructiveHint=true and openWorldHint=true, so the external side effect is partly covered. The description adds that a customer email is sent, but omits the stage mutation itself, the optimistic-concurrency requirement (expectedRowVersion/expectedStage must match current state or the call presumably fails), and any irreversibility or failure behavior.

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?

A single short sentence with no filler, front-loaded. It is efficient, though efficiency here reflects under-specification rather than disciplined brevity.

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 destructive, open-world, five-required-parameter mutation with no output schema and no parameter documentation, the description omits the state transition, the concurrency guard semantics, and the email's relationship to the mutation. An agent has almost nothing beyond raw enums to call this correctly.

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?

Five required parameters with 0% schema description coverage, and the description mentions none of them. It gives no meaning for stage vs. expectedStage, no explanation of the row-version guard, and no note on the 6000-character note field.

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 name and schema say this tool transitions a record's stage (IN_PROGRESS/READY → READY/COMPLETED), but the description only mentions emailing the customer a progress update. It describes an apparent side effect rather than the core mutation, so an agent cannot reliably infer what the tool actually does from the text.

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?

"after approval" is a weak timing hint, but it does not say which approval artifact is needed (get_approval? wait_for_decision?) nor distinguish this from siblings like send_approval_request or create_approval_request, which also involve customer email. No when-not guidance.

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