Prepare customer report retry

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false, and destructiveHint=false, so the safety envelope is covered. The description adds useful context ('stage', retrying, private support tracker), but says nothing about the non-idempotent retry risk or what confirm/cancel does next.

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?

One compact sentence with the action front-loaded and no filler. Minor jargon ('ReceiptCal') aside, every phrase carries information.

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 staging/mutation tool with no output schema, the description is minimally adequate: annotations cover the safety profile and the description conveys intent. It omits the confirm/cancel follow-up and the non-idempotent retry behavior, which an agent needs to use it 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?

The single report_id parameter has 0% schema description coverage; the UUID regex conveys format but no meaning or provenance. The description refers to 'a failed ... customer report' implicitly, but never clarifies that report_id must identify that failed report, so meaning is largely left to inference.

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 names a specific verb (stage retrying), resource (a failed ReceiptCal customer report), and destination (the private support tracker), so the agent can distinguish it from prepare_create_customer_report. It doesn't explicitly name the differing sibling, but the 'retry a failed report' framing is distinctive.

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?

No when-to-use guidance and no stated alternatives. It implies applicability only to already-failed reports, but the agent is not told how this differs from prepare_create_customer_report or get_customer_report_status, nor that staging likely precedes confirm_action.

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