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

Annotations only flag destructive/readOnly/idempotent, but the description adds real behavioral context: side effects on the recipient, three distinct rate limits (max 5/day, one per recipient/day, no duplicate live offer for a date), and the prerequisite "Allow my assistant to act" switch. That is substantial disclosure beyond the structured fields, with no contradiction of the annotations.

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-loads the purpose before the em dash, then packs constraints into a tight clause series with no filler. It reads as one long run-on sentence, which slightly hurts scannability, but nearly every clause carries an operational constraint.

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?

For a mutating tool with no output schema, the description covers side effects on the recipient, eligibility, rate limits, and prerequisites. It could say what the caller receives back (e.g. whether an offer id or pending booking reference is returned), but everything needed to call it correctly is present.

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 description coverage is 100%, with units, formats, and ranges already documented for all seven parameters (GBP 1-100000, YYYY-MM-DD, HH:MM, slug/id). The description adds no parameter-level detail, so the baseline of 3 applies.

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 and resource ("Send a booking offer") plus the target actor ("another GigXchange member"), and immediately clarifies the recipient-side effect (pending booking, notification, offer card). This lets an agent distinguish it from respond_to_booking, counter_booking, and apply_to_gig 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?

Gives explicit eligibility rules: supported role pairs (venue/promoter/organiser to artist, artist to venue/promoter, promoter to venue) and a clear when-not (offers involving an agent are app-only). It does not name the sibling alternatives (e.g. counter_booking for negotiating back), so routing among similarly named booking tools is left partly to inference.

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