easytable_modify_booking

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

Annotations indicate non-read-only, open-world, non-idempotent. The description adds critical behavioral details: the dry-run preview mode without confirm:true (no network call) and the need for a Turnstile token from the signed-in widget tab. No contradictions with 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?

The description is extremely concise, using two sentences plus a brief clause. Every sentence provides essential information without fluff, and the structure is front-loaded with the purpose.

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?

Given 14 parameters and no output schema, the description covers the key behavioral aspects (dry-run, token requirement) but does not specify the output format or semantics. This is adequate but not exhaustive.

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 100%. The description adds context beyond the schema for 'confirm' (dry-run) and 'existing' (source from easytable_find_bookings), improving understanding without repeating all parameter details.

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 modifies an existing booking, specifying the modifiable fields (date/time/party size/details). It is distinct from sibling tools like easytable_cancel_booking and easytable_create_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?

The description explains how to get the booking ID from easytable_find_bookings and the dry-run vs confirm behavior. It provides clear when-to-use guidance, though it does not explicitly discuss when not to use or alternatives beyond the sibling tools.

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