createBooking

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

Discloses that conflict detection runs automatically and the call fails on overlap. No annotations exist, so the description carries full burden; it adequately informs about behavior but could mention side effects like creation persistence.

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?

Structured into clear modes with numbered instructions. While well-organized, it is slightly verbose; concise mode labels and a list could reduce length without losing meaning.

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 11 parameters, no output schema, and two modes, the description provides sufficient workflow context and conflict detection notes. It lacks return value details but compensates with mode-specific parameter guidance.

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%, so baseline is 3. The description adds value by grouping parameters by mode and explaining relationships (e.g., proposalId and slotId come from getProposal), exceeding the schema's individual descriptions.

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's purpose: to confirm a meeting. It explains two distinct modes (proposal-based and direct) and how to use each, effectively distinguishing this from siblings like createProposal and cancelBooking.

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 each mode, including prerequisite steps (e.g., calling getProposal for proposal-based mode). However, it does not explicitly state when not to use the tool, but the context makes it clear that this is for finalizing a booking.

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