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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering safety and non-destructive behavior comprehensively. The description adds value by specifying the return shape (name, state, country, coordinates) and its role in lookup, complementing rather than contradicting the 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?

Two concise sentences, zero wasted words. The first sentence states purpose and output, the second gives the practical use case. Front-loads the action and result, then provides context.

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?

Description covers purpose, output shape, and use case; output schema exists so return values don't need explanation. The undocumented `p` parameter is a gap, and there's no explicit statement about result limits or matching behavior, but overall the description is sufficient for a lookup tool with rich annotations and output schema.

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 67% with descriptions for `name` (with example) and `country` (with format constraint 'DE not Germany'). The description adds the resolution-use-case context, but the `p` parameter remains undocumented in both schema and description. The description mostly reinforces what the schema already communicates, hence baseline 3.

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 verb+resource ('Search setlist.fm for cities by name or country'), specifies what's returned (city name, state, country, geolocation coordinates), and distinguishes its purpose from venue/setlist searches. Also differentiates from the 'countries' sibling by saying to call it for the country code list.

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?

States a concrete use case ('resolving city identifiers before searching setlists or venues') and implies usage context. It doesn't explicitly say when NOT to use it or name alternative tools for the main search scenario, but the resolved-identifier purpose and the explicit reference to `countries` provide reasonable guidance.

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