complete_booking

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals key side effects: freeing the driver and awarding +10 score. It does not mention irreversibility or prerequisites, but the disclosed effects go beyond the basic schema and help the agent understand consequences.

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 a single, front-loaded sentence with no filler. It efficiently states the action, condition, and consequences in a clear order. Every word earns its place, making it an excellent example of concise writing.

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?

The tool is simple (one parameter, no output schema), and the description covers the action, trigger, and effects. While it could mention whether the booking must be in a specific status, the provided context is sufficient for an agent to use it correctly. The description is complete enough for the tool's complexity.

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%, and the parameter description 'Booking ID to complete' is simple but adequate. The tool description does not add further nuance about the parameter, but since the schema is clear and the tool only has one parameter, the baseline score of 3 is appropriate.

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 action: 'Mark a booking as completed' when the guest reaches the destination. This specific verb+resource distinguishes it from sibling tools like cancel_booking or create_booking, and the additional effects (frees driver, awards score) further clarify its purpose.

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 provides a clear usage context: use this when the guest reaches the destination. It does not explicitly exclude alternative scenarios like cancellations, but the trigger condition is explicit enough to guide the agent. Sibling tools like cancel_booking handle other lifecycle events, so the context is sufficiently differentiated.

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