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 of behavioral disclosure. The description only says 'Create a new booking' and lists arguments; it does not disclose side effects (e.g., whether a payment is initiated), permission requirements, reversibility, or what the response contains. For a mutation tool, this is a significant transparency gap.

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 front-loaded with a one-sentence purpose, followed by a structured Args list. It is informative without excessive verbosity, though the Args block is somewhat long. No wasted sentences, but the formatting is mildly repetitive (parameter names repeated in descriptions).

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 has 6 parameters including a nested structure, yet no output schema and no annotations. The description covers all parameters well, but it omits return value/response behavior, potential error conditions, and usage context. For a create action this is incomplete—an agent would not know what the tool returns or whether it can fail due to unavailability.

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 description coverage is 0%, so the description must compensate, and it does thoroughly. It explains each parameter, including the nested passenger dictionary with all required fields (name, phone_number, etc.), provider examples, date format (YYYY-MM-DD), and optional nature of origin_id, destination_id, and travel_date. This adds substantial meaning beyond the bare schema.

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 opens with a clear, specific verb+resource: 'Create a new booking.' This unambiguously distinguishes it from sibling tools like get_booking_history, search_trips, and initiate_payment. The purpose is immediately apparent.

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 implies when to use the tool (when creating a booking) but offers no explicit guidance on alternatives, prerequisites, or when NOT to use it. For example, it doesn't mention that search_trips should be used first to obtain a trip_id, nor does it reference sibling tools for origins/destinations. The usage is implied rather than spelled out.

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