get_reservations

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

Annotations correctly indicate a safe read operation, so the description adds no safety warning. However, the false claim about filtering by 'guest name' is misleading about actual behavior, and there is no mention of pagination behavior or default limits beyond the schema.

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, short sentence and is front-loaded with the main action. It contains no redundant words, but the inaccuracy about 'guest name' prevents a perfect score.

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?

With 8 parameters, no output schema, and a sibling tool for advanced search, this description is incomplete. It omits pagination/skip-limit usage, provides no differentiation from 'search_reservations', and includes an incorrect filter dimension, leaving the agent under-informed.

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 coverage is 100%, so the baseline is 3, but the description actively misleads by referencing a 'guest name' filter not present in the schema, and it vaguely says 'listing' instead of the actual parameter name 'listingId'. It adds no useful semantic value and introduces confusion.

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 identifies the action ('Fetch reservations') and resource ('from Guesty'), but it lists 'guest name' as a filter option even though no such parameter exists in the schema. This inaccuracy undermines clarity, and it does not differentiate from the sibling tool 'search_reservations'.

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 provides no guidance on when to use this tool versus alternatives like 'search_reservations'. It only states what filters are possible, not the appropriate context or exclusions.

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