create_reservation

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

With no annotations provided, the description carries full burden but only states it 'creates' a reservation without disclosing behavioral traits like whether this is a transactional operation, what happens on success/failure, if it requires authentication, or any rate limits. It mentions required inputs but not the operational context.

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, well-structured sentence that efficiently communicates the tool's purpose and key requirements. It is front-loaded with the main action and avoids unnecessary elaboration, making it easy to parse.

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 complex mutation tool with 13 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral aspects, error handling, return values, and doesn't fully compensate for the schema's incomplete coverage, leaving the agent with significant gaps.

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 description lists categories of required inputs (vehicle, location, dates, driver info), which adds some meaning beyond the schema's 62% coverage. However, it doesn't detail specific parameters or their relationships, leaving gaps for the 38% of schema parameters without descriptions (e.g., driver_age, discount_code).

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 action ('Create a new Enterprise Rent-A-Car reservation') and specifies the required components (vehicle selection, location details, dates, driver information). It distinguishes from siblings like 'modify_reservation' and 'cancel_reservation' by focusing on creation, though it doesn't explicitly contrast with them.

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 mentions 'Requires' to list necessary inputs, but provides no guidance on when to use this tool versus alternatives like 'modify_reservation' or 'search_vehicles'. It lacks explicit context about prerequisites or scenarios where this tool is appropriate.

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