Get Reservation

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds value by enumerating return fields (guest, property, dates, channel, payment status, notes), which helps set expectations. No contradictions, but could mention no side effects.

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 concise sentences (English and Spanish) front-load the essential information. No wasted words; every sentence serves purpose. Bilingual addition is justified for multi-language context.

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?

Given the presence of an output schema, the description need not detail return values but elegantly summarizes the key fields (guest, property, dates, channel, payment status, notes). Single parameter, simple operation—description is complete for agent to understand usage.

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%: the 'id' parameter is described as 'Reservation ID / ID de reserva'. The description only mentions 'by ID' without adding new semantics. Baseline 3 is appropriate as description does not enhance parameter understanding beyond the 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?

Clearly states 'Get a single reservation by ID' with specific verb and resource. Distinguishes from sibling list_reservations (which retrieves multiple) and other get_* tools by focusing on reservation context. Lists return fields for specificity.

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?

Implicitly clear: use to retrieve one reservation by ID. However, lacks explicit when-to-use vs alternatives (e.g., list_reservations for all reservations) and no when-not-to-use guidance. Still, the purpose is unambiguous.

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