Confirm Booking

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

Annotations already indicate this is destructive (destructiveHint=true) and not read-only. Description adds beyond annotations by specifying prerequisites for headless submit, which is non-obvious 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?

Two short sentences, front-loaded with main action. Some technical jargon ('headless submit', 'raw upstream payload') but still efficient.

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?

No output schema exists, yet description omits what the tool returns on success or failure. Given only one parameter, more detail about expected outcomes or side effects is needed.

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 0% and description does not explain the single parameter 'draftId' beyond its name. The description adds no semantic detail about the parameter's format, purpose, or constraints.

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?

Clearly states the verb 'Confirm' and resource 'prepared booking draft'. Distinguishes from siblings like 'prepare_booking' and 'confirm_cancellation' by specifying it operates on a draft.

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 condition 'Headless submit only runs when experimental writes are enabled and the draft contains a raw upstream payload', which guides when the tool works. Lacks explicit alternatives or when-not scenarios, but the context is helpful.

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