shelf_reserve_booking

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's 'DRAFT' qualifier adds a real behavioral constraint (the target booking must be in draft state), but it omits what the reservation does to the booking's state, whether it is reversible, and any permission requirements.

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?

A single short sentence with no filler, and the state qualifier is front-loaded. It is concise, though the brevity borders on under-specification rather than pure economy.

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?

For a mutation tool with no output schema and a partially documented schema, the description should explain the draft precondition, the resulting state, and failure behavior. It delivers only the draft qualifier, leaving most of what an agent needs to invoke it correctly unstated.

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 67%, and the required parameter bookingId has no description in the schema at all; the tool description does nothing to clarify it (e.g., that it must reference a draft booking). The description adds no meaning beyond what the schema partially provides.

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?

States a specific verb ('Reserve') and resource ('booking'), and adds a state qualifier ('DRAFT'). However, it doesn't distinguish this from close siblings like shelf_create_booking, shelf_checkout_booking, or shelf_update_booking, leaving the agent to infer which booking-transition tool applies.

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 explicit when-to-use or when-not-to-use guidance. The word 'DRAFT' hints at a precondition (the booking must be a draft), but the description never states this as a requirement, nor does it name an alternative tool for non-draft bookings.

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