vt_get_availability_schedule

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's main behavioral contribution is clarifying the return data (seasons, times, pricing). It does not disclose additional traits like rate limits or error conditions, but with annotations covering safety, a score of 3 is appropriate.

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 concise sentences plus a short note, front-loading the core purpose and then adding a critical usage hint. Every sentence serves a purpose with no redundancy.

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?

Despite lacking an output schema, the description comprehensively lists what the tool returns (seasons, days, start times, unavailable dates, per-age-band pricing) and addresses the currency conversion caveat. For a single-parameter, read-only tool, this is fully sufficient.

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% for the single parameter product_code, and the schema description already states its purpose. The description adds value by providing an example ('e.g. 5010SYDNEY'), which helps agents understand the expected format beyond the regex pattern.

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 availability schedule and pricing for a Viator product, listing specific data elements (seasons, days of week, start times, unavailable dates, per-age-band pricing). This distinguishes it from siblings like vt_get_product or vt_get_exchange_rates.

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 includes a note advising that prices are in the supplier's currency and recommending vt_get_exchange_rates for conversion, providing explicit guidance on when to use an alternative. However, it doesn't specify when not to use this tool or compare to other siblings directly.

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