Get Fan Zones

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

Description adds value beyond readOnlyHint annotation by detailing return payload (venue details, capacity, hours, etc.) and filtering behavior. Does not contradict annotations. Transparent about scope and limitations.

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?

Single sentence, front-loaded with core purpose, followed by key return fields and filter options. No wasted words, though could be slightly more structured (e.g., bullet list). Efficient and clear.

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?

No output schema, so description fully compensates by listing return details (venue, capacity, hours, etc.) and all three optional filter parameters. Covers what the tool returns and how to use it, complete for a read tool with good annotations.

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 baseline 3. Description adds minor semantic detail (city case-insensitivity, venue_id returns fan zones for that stadium's city) but mostly restates schema. Adequate but not richly informative.

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 it returns 'Official FIFA Fan Festival and fan zone locations' with specific details. Verb 'Get' + resource 'Fan Zones' is precise and distinguishes from siblings like get_nearby_venues which cover different venue types.

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?

No explicit when-to-use or alternatives guidance. The description implies usage for retrieving fan zone information but does not mention when not to use or compare with siblings. Adequate but missing exclusion context.

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