gyg_get_tour_availability

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

Annotations mark readOnlyHint=true, and the description's 'Get booking availability' aligns. The description adds context on the kind of data returned (categories, addons, dates), which is consistent with a read operation and gives agents a better understanding of the response.

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, well-structured sentence that immediately states the purpose and differentiates from a sibling. No redundancy or unnecessary words.

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 lightweight availability tool with only two parameters and no output schema, the description covers the key outputs and use case. It could mention pagination or data format, but the brevity is appropriate for the tool's simplicity.

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%, with both parameters already described in the schema (tourId as numeric ID, language with default). The description does not add extra parameter information, so it meets the baseline without improvement.

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 tool retrieves booking availability, listing specific outputs (participant categories, addons, available dates). It distinguishes from the sibling gyg_get_tour_options by noting this tool is lighter and for when only 'when can I go' is needed.

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?

Explicitly tells when to use this tool versus the alternative gyg_get_tour_options: 'Lighter than gyg_get_tour_options when you only need "when can I go".' This provides clear decision guidance.

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