afl_venues_list

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint), the description adds useful context: 'Auth: none needed' and the exact return structure `{venues:[{id, providerId, name, location, state, timezone, landOwner}]}`. This discloses the response shape and access requirements, adding value beyond annotations.

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 concise and front-loaded: it leads with the core action, then provides the return shape and auth requirement in a structured format. Every sentence earns its place without fluff.

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 list tool with optional pagination parameters, the description is largely complete: it states the resource, fields, return structure, and auth. It could optionally mention pagination behavior, but the schema already covers that. The absence of an output schema is mitigated by the inline return type.

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?

The input schema already has 100% description coverage for both parameters (page: 'Zero-based page number.', pageSize: 'Rows per page.'). The description adds no parameter-specific information beyond what is in the schema, so the baseline of 3 applies.

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's function: 'List venues (191) incl. location, state, timezone, landOwner.' The verb 'List' plus the resource 'venues' makes the purpose explicit. It also distinguishes from the sibling afl_venue_get by indicating this is a bulk list operation with specific fields.

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 provides no guidance on when to use this tool versus alternatives like afl_venue_get. It only states 'Auth: none needed', which is not usage guidance. No mention of pagination or when the list is appropriate.

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