get_reservation

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

With no annotations provided, the description carries full burden. It clearly indicates this is a read operation ('Look up'), which is helpful, but doesn't disclose other behavioral traits like authentication requirements, rate limits, error conditions, or what data is returned. It adds basic context but lacks operational details.

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?

Single sentence, zero waste. Every word earns its place: verb, resource, and required identifiers are front-loaded. No redundant information or fluff.

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 simple lookup tool with 2 parameters and 100% schema coverage, the description is adequate but minimal. No output schema exists, so the description doesn't explain return values (e.g., reservation details). With no annotations, it could benefit from more behavioral context, but it meets basic needs.

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 100%, so the schema already fully documents both parameters. The description mentions the parameters but doesn't add meaningful semantics beyond what's in the schema (e.g., format examples, validation rules). Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Look up') and resource ('existing Hertz reservation'), and distinguishes it from siblings like 'create_reservation' or 'modify_reservation' by specifying it's for retrieval only. It precisely identifies the lookup method using confirmation number and last name.

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 usage context (when you have a confirmation number and last name to retrieve a reservation), but doesn't explicitly state when to use this versus alternatives like 'search_vehicles' or 'get_vehicle_details'. No exclusions or prerequisites are mentioned.

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