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

Goes well beyond annotations by disclosing the atomic hold guarantee, the absence of upfront confirmation, and venue-dependent support. These are critical behaviors not apparent from the schema or annotation hints.

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 description is dense with important details but somewhat rambling. The opening 'REAL action:' is redundant, yet every sentence adds operational value. Could be structured better but remains efficient.

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?

Covers the main use cases, atomicity, consent behavior, and venue limitations, which is strong for a tool with no output schema. However, it does not describe the return format or how a consent link would be handled beyond mentioning it, leaving a minor gap.

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?

With 0% schema coverage, the description compensates by specifying the item structure (doctor: {date, from, to}) and the same-day constraint. It does not fully define provider_id or enumerate all possible item types, but provides meaningful context.

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 clearly states the tool reschedules a booking at a venue, specifying the atomic same-day mechanism. It distinguishes from siblings by explicitly directing different-day cases to 'book again' and hostel cases to 'cancel and book again'.

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?

Provides explicit when-to-use and when-not-to-use guidance: same-day rescheduling uses this tool, different-day means book again, and unsupported venues (hostels) require cancel+book. Also states the no-consent-required policy and consent-link exception.

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