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

Beyond the annotations (destructive, non-readOnly, idempotent) the description discloses a fee-match guard that refuses stale calls, a rate limit of 3 declines per day, a side effect (accepting can start the payment flow), a relayed message to the other party, and an enabling precondition (the 'Allow my assistant to act' switch). These are exactly the hidden traits an agent needs.

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 core action and scope, then each following clause adds a distinct precondition, guard, or consequence. No filler sentences; every clause carries operational information.

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 no output schema and a simple flat param set, the description supplies everything else needed to invoke this mutation correctly: who can call it, which offers qualify, the fee-match guard, the decline rate limit, the decline note requirement, and the payment side effect.

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 75%, with the action enum and booking_id already documented. The description still adds real meaning: it explains expected_fee is a validation guard (must equal the current fee or the call is refused) and that note is mandatory when declining and is relayed to the counterparty.

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 pair (accept/decline) and an equally specific resource (a booking offer), then immediately scopes it: only offers the member RECEIVED, never one they sent. That scope clause cleanly separates it from siblings like make_offer and counter_booking without needing to read 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?

Gives explicit when-to-use (respond to a received offer) and a strong when-not ('never one they sent'), plus declining constraints. It stops short of naming the alternative tools (e.g. counter_booking for a counter-offer), so it is clear context with an exclusion rather than a full routing map.

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