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

With no annotations, the description fully discloses key behaviors: modifying a confirmed booking cancels it and returns a new booking_id; for needs_input, passing accept_option_index confirms immediately. Missing details on side effects or authorization.

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 tight sentences that quickly convey the primary use case and two sub-scenarios. No redundant 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?

Covers the main scenarios but omits return value details (e.g., new booking_id structure) and potential errors. Given no annotations and 5 parameters, additional context would be helpful.

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 40%. The description adds context for accept_option_index and datetime/party_size but does not explain window_minutes or booking_id. Partially compensates for low coverage.

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 verb 'Amend' and the resource 'booking', and distinguishes between two distinct scenarios (needs_input and confirmed bookings), making the purpose unambiguous and differentiating from siblings like cancel_booking.

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 guidance on when to use for needs_input and confirmed bookings, and explains how to modify vs accept. However, it does not explicitly state when not to use or mention alternatives like place_booking.

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