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

Annotations already declare non-read-only, idempotent and non-destructive, but the description adds real behavioral context: the counter-proposal loop, that a confirmed booking stays as agreed until the business agrees, that the end time preserves the booking's length, and that the request escalates to a human (passed_on) after a few rounds. Auth requirements for key/pass are left to 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?

The key constraint is front-loaded in the first clause, and every sentence carries behavioral information. The prose is dense and clause-heavy ('After a few rounds, or past the changes a booking may have...'), which lowers readability, but there is no filler.

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 7-parameter negotiation tool with no output schema, the description covers the negotiation lifecycle, the escalation path and the response expectations well enough to call it correctly. Only the credential mechanics (pass/key exchange) are left entirely to the schema, which is acceptable.

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 71% and the description reinforces the most consequential parameter, start_time, by tying it to check_availability and stating the end follows the service length. It adds nothing for note, key, pass, access_token or idempotency_key, which the schema mostly documents, so this is baseline-plus rather than compensating for gaps.

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+resource — asking the business for a different time than the one proposed — and immediately names the sibling check_availability as the source of valid start times. It is clearly distinguishable from accept_offer/make_offer, though it never explicitly contrasts itself with those siblings.

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?

It gives an explicit prerequisite ('start_time must be one of the free times check_availability lists') and describes the two resulting contexts: a pending proposal versus a confirmed booking. It does not say when to prefer this over make_offer or accept_offer, so it stops short of full when/when-not guidance.

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