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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantially more: the two-phase confirm gate, the fact that only confirm=True returns success=true, the required auth + write:listings scope, and who the actor is (seller rejecting a buyer's offer on their own listing). That is exactly the extra context annotations cannot convey.

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?

Front-loaded with the source system and the two-phase rule before the supporting details. It is somewhat dense and the repeated 'two-phase' phrasing plus the final seller-facing sentence are slightly redundant, but nothing is wasted.

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?

Output schema exists so return values need not be explained. For a destructive, auth-gated, three-required-parameter mutation, the description covers trigger, safety protocol, permissions, and actor role — an agent has everything needed to call it correctly and safely.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by tying confirm=False to a preview and confirm=True to an actual reject that is the only path to success=true, and by positioning offer_uuid/identifier in the seller's listing context.

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?

States a specific verb (reject) on a specific resource (a buyer's offer/bid on the seller's own listing), plus the underlying system ('XP live offer book'). It is trivially distinguishable from the sibling accept_offer.

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?

Gives an explicit when-to-use trigger (authenticated seller rejecting a bid, with the 'reject the lowball offer' example) and a hard when-not/procedural rule: never call without the two-phase preview-then-confirm flow. The preview/confirm sequencing is spelled out step by step.

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