gyg_get_tour_options

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that it lists options with optional date range filtering, but does not disclose other behavioral traits such as pagination, rate limits, or auth requirements. With annotations present, the description provides minimal additional behavioral context.

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 is concise (17 words) and front-loaded with the essential purpose. Every word serves a clear function 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?

Given the absence of an output schema and the complexity of 7 parameters (1 required), the description is adequate but incomplete. It does not describe the output format or pagination behavior, which would help the agent understand what to expect. The description covers the core purpose but lacks detail on results.

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 baseline is 3. The description does not add meaning beyond the schema; it only gives high-level context about the tool's output. For example, it mentions 'ticket types, times, languages' but these are not parameter-specific details.

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?

Description clearly states that the tool lists bookable options of a tour, specifying the types of options (ticket types, times, languages) and optional date range. It does not explicitly differentiate from sibling tools like gyg_get_tour or gyg_get_tour_availability, but the name and description make its unique purpose evident.

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?

Description provides no guidance on when to use this tool versus alternatives, nor does it specify prerequisites or limitations. It simply states what the tool does without contextual advice for the agent.

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