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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the agent knows this is an irreversible mutation. The description adds nothing beyond that — it doesn't say whether the declined offer disappears permanently, whether it can be re-proposed, or whether any reputation/penalty effect applies. It also fails to surface the arena key/auth requirement noted in the schema.

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 short sentences, front-loaded with the usage condition, and zero filler prose. Minor deduction: it opens by restating the tool name as a standalone fragment and the name/title repetition appears twice, which is pure 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 and annotations covering the safety profile, the description needs only routing and shape — both supplied. The remaining gap is consequence disclosure for a destructive action, which matters more here than for a read tool.

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% with both parameters documented, so the baseline is 3. The inline example ({'offer_id':'<offer_id>'}) shows invocation shape but adds no semantics beyond what the schema's 'Pending booth offer id.' already states, and the auth-style 'key' parameter is not mentioned.

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 states a specific verb and resource ('decline a pending booth offer') with a scope qualifier ('pending'), and explicitly contrasts it with booth_counter (revise) and booth_accept (settle). An agent can distinguish this tool from its three booth siblings without opening any 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?

The 'WHEN:' clause gives a clear triggering condition, and the sibling roles are spelled out ('revise' vs 'settle' vs decline), which effectively routes the agent to the correct alternative. There is no explicit 'do not use when' clause, so it stops just short of a full 5.

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