get_reservations

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

No annotations are provided, so the description carries full burden. It states the tool gets reservations with optional filtering, but doesn't disclose behavioral traits such as whether it's read-only, pagination behavior, rate limits, authentication needs, or what happens if no date is provided (though implied by 'returns all reservations'). This leaves significant gaps for a tool that likely interacts with reservation data.

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, efficient sentence that front-loads the core purpose ('Get all room reservations') and adds optional filtering information. There is no wasted verbiage, making it highly concise and well-structured.

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 no annotations, no output schema, and a simple input schema, the description is minimally adequate but incomplete. It covers the basic purpose and parameter implication, but lacks details on behavior, output format, error handling, or sibling tool differentiation, which are important for effective use in this context with multiple related tools.

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 fully documents the single parameter 'date' with its format and default behavior. The description adds no additional parameter semantics beyond what's in the schema, such as examples or edge cases, meeting the baseline for high schema coverage.

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 'Get' and resource 'room reservations' with optional date filtering. It distinguishes from siblings like 'get_reservation' (singular) and 'get_reservations_by_room/user' by not specifying filtering by room or user, but doesn't explicitly contrast with 'get_day_overview' or 'get_available_rooms' which might overlap in purpose.

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 when needing all reservations with optional date filtering, but doesn't explicitly state when to use this versus alternatives like 'get_reservations_by_room' or 'get_day_overview'. No guidance on prerequisites or exclusions is provided.

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