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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description builds on that with the crucial detail that only confirm=True submissions return success=true, plus the required auth and write:listings scope. This is exactly the behavioral context an agent needs before mutating state.

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?

Information is front-loaded and mostly tight, but the 'Do not use without the two-phase preview-then-confirm flow' sentence restates the earlier confirm=False/confirm=True instruction, adding mild redundancy.

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?

With an output schema present, return values need not be explained. Auth scope, destructive nature, two-phase flow, alternatives, and audience restrictions are all covered, leaving nothing an agent needs missing.

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 parameters are already documented, giving a baseline of 3. The description adds real nuance by tying confirm to the two-phase preview/confirm semantics and clarifying that confirm=False is a non-mutating preview, which slightly exceeds the schema text.

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) and resource (a specific bid/offer on the seller's listing) on the XP live offer book, and clearly distinguishes itself from accept_offer and buyer-side tools. An agent can tell what this does 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?

Explicitly states when to use (authenticated seller rejecting a bid), when not to use (casual ticket buyers; the standard purchase path), and names alternatives (search_events, get_ticket_listings). The two-phase preview-then-confirm flow is spelled out as a hard requirement.

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