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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is largely carried by structured data. The word "settles" hints at finality, but the description does not explicitly say the acceptance is irreversible, what state changes, or what auth is needed beyond the schema's key note.

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?

Short and front-loaded: purpose, then WHEN, then differentiation, then an example. The leading repetition of the tool name "booth_accept." is dead weight, but everything else earns its place.

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 a documented output schema, rich annotations, and full parameter descriptions, the description only needs to cover purpose and routing, which it does. The missing piece is a note on the irreversibility implied by the destructive hint, which would make it complete.

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 both offer_id and key are already documented in the input schema — this is the baseline 3 case. The inline example call adds a small amount of concrete usage illustration but no syntax or semantic detail beyond the schema.

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 gives a specific verb and resource: the recipient accepts a pending booth offer and it settles. It names the sibling alternatives (booth_decline / bazaar_resolve_proposal) so an agent can tell it apart, though it does not explain the actual decision criteria between them.

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?

"WHEN: recipient accepts a pending booth offer" is an explicit trigger condition, and the description points at booth_decline and bazaar_resolve_proposal as the alternative tools. It stops short of stating when not to use it or what the alternatives do, so it is clear but not fully directive.

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