create_booking

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

No annotations are provided, so the description carries the full burden. It mentions 'instant confirmation', hinting at immediate results, but doesn't disclose critical behavioral traits such as whether this is a write operation (likely, given 'book'), authentication needs, error handling, or rate limits. The description is too brief to adequately inform the agent about the tool's behavior.

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—just four words—and front-loaded with the core action. There's no wasted language, making it easy to parse quickly. However, this brevity comes at the cost of completeness, but for conciseness alone, it's optimal.

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 the complexity (a booking tool likely involving writes), no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't explain what happens after booking (e.g., confirmation details, errors), prerequisites, or how it interacts with sibling tools. The agent lacks sufficient context to use this tool effectively.

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?

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description doesn't add any meaning about the 'property_id' parameter—it doesn't explain what a property ID is, how to obtain it, or its format. This leaves the parameter undocumented, failing to compensate for the low schema 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 'Book with instant confirmation' states the action (book) and a key feature (instant confirmation), but it's vague about what resource is being booked. It doesn't distinguish from sibling tools like 'check_availability' or 'search_properties' that might involve booking-related functions. The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., checking availability first), exclusions, or how it relates to siblings like 'check_availability'. The description implies it's for booking, but without context on timing or constraints.

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