Get Venues

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

Annotations already declare readOnlyHint=true, so the description is not required to repeat that. The description adds value by specifying that the tool returns 'full venue details including capacity, coordinates, and notable events', which provides behavioral context beyond the annotation.

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?

Two sentences, first sentence states the core purpose, second gives details on filtering and output. Every word earns its place with no redundancy. Front-loaded with the action verb 'Query'.

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 simple query tool with 3 optional parameters and no output schema, the description provides sufficient information about what the tool does and returns. However, it could be enhanced by mentioning how to choose between this and 'get_nearby_venues' for completeness.

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 full descriptions for each parameter. The description does not add new meaning to the parameters beyond summarizing the filter options. Baseline score of 3 is appropriate as the schema already documents the parameters well.

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 verb 'Query', the resource 'venues', and specifies the context 'FIFA World Cup 2026'. It also lists the filter dimensions (country, city, region) and the output fields (capacity, coordinates, notable events). This distinguishes it from siblings like 'get_nearby_venues' which likely focuses on proximity-based queries.

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 implies usage for querying venues with optional filters, but it does not explicitly state when to use this tool versus alternatives like 'get_nearby_venues' or 'get_fan_zones'. No exclusions or prerequisites are mentioned.

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