get_reservation

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

No annotations are provided, so the description carries full burden. It discloses authentication needs ('Requires being logged in'), which is useful. However, it lacks details on behavioral traits like read-only vs. mutative nature, error handling, rate limits, or return format. For a tool with zero annotation coverage, this is a significant 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 two sentences, front-loaded with the core purpose and followed by a prerequisite. Every sentence earns its place with no wasted words, making it appropriately sized and efficient.

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 1 parameter with full schema coverage and no output schema, the description is minimally complete. It covers authentication needs but lacks details on return values, error cases, or behavioral context. For a simple lookup tool, it's adequate but has clear gaps in transparency.

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%, with the parameter 'confirmationNumber' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., format examples or constraints). Baseline 3 is appropriate when the 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 verb ('Look up') and resource ('a specific Hilton reservation'), specifying it's by confirmation number. It distinguishes from siblings like 'get_stay_history' (multiple reservations) or 'search_hotels' (hotel search), but doesn't explicitly name alternatives. The purpose is specific but could be more differentiated.

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 by stating 'Requires being logged in', which is a prerequisite. However, it doesn't explicitly say when to use this vs. alternatives like 'get_stay_history' for past reservations or 'modify_reservation' for changes. The guidance is implied but incomplete.

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