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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent already knows the operation is safe. The description adds the filter for published venues, which is behavioral context not in the annotations. However, it does not mention pagination behavior or that only cities with published venues are included, which is the key filter. The added context is useful but minimal beyond the safety profile.

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, efficient sentence that front-loads the core purpose. Every word is functional, with no redundancy or filler.

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 tool is a simple list with an output schema and fully documented parameters, the description is nearly complete. The main missing piece is explicit guidance on when to choose this over similar search tools, but that is a minor gap for a low-complexity tool.

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 schema fully describes both parameters (limit and cursor). The description adds the filter on published venues, which affects which cities appear in results, but it doesn't add further parameter-level detail beyond the schema. Since coverage is high, the baseline of 3 is raised because the description adds a meaningful semantic constraint.

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 'list' and the resource 'cities', and specifies the exact criterion: cities with at least one published venue. This distinguishes it from siblings like search_destinations or list_* tools that may have different scopes.

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 clear context on what it returns (cities with published venues) but does not explicitly discuss when to use this tool versus alternatives. Given siblings like search_destinations exist, more guidance on choosing this simple list over search would improve the score.

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