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

Beyond the annotations it discloses the side effect ("a failure queues a re-check of the link"), the write-once constraint, the 72-hour window, and the authorization scope (signed-in shopper only). That is exactly the context the destructiveHint/idempotentHint flags cannot convey on their own.

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?

Three tight sentences, front-loaded with what is reported, then constraints, then the semantic boundary. Every clause carries distinct information; nothing is repeated from the schema or annotations.

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 2-parameter write with no output schema, the description covers purpose, scope, timing, and the failure side effect. It stops short of saying what the call returns or what error surfaces on a duplicate report or a call after 72 hours.

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 carry the load. It enriches the outcome values ("failed (dead link or broken form)") and the once-per-action framing explains action_id's role, but it never says where action_id comes from or what shape it takes beyond the schema's uuid pattern.

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?

Specific verb plus resource: reports whether a confirmed booking, order, or quote handoff completed, failed, or was abandoned. The enumerated outcome vocabulary lets an agent distinguish it from confirm_*_handoff siblings and from get_action_status without opening the schema.

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?

"Once per action, within 72 hours, for this signed-in shopper only" gives concrete preconditions for calling it. The closing sentence routes the agent away from misuse ("not a receipt: it never completes a booking or backs a review"), implicitly pointing at confirm_booking and submit_verified_review, though no sibling is named explicitly.

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