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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true). The description adds genuinely useful context beyond them: this is a static curated snapshot (87 metro areas as of a date) rather than live search, and it lists the verticals each city supports. No auth or rate-limit details, but for a read-only directory that gap is minor.

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 with no waste. The resource identity is front-loaded, followed by the field list and the integration hint, so the most important information leads.

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?

An output schema exists, so return values need not be fully explained, and the description still summarizes contents and the seatgeek_events_near pairing. It does not explicitly state the list is unfiltered/exhaustive, but for a zero-parameter read-only directory the definition is essentially complete.

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 tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter syntax and instead explains the return contents and the downstream join key, which is the useful information for a no-arg tool.

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 states a specific resource (SeatGeek's curated browse-by-city directory) and enumerates the exact fields returned (id, name, state, country, coordinates, supported verticals). An agent can tell this apart from sibling tools like seatgeek_categories or seatgeek_venue without opening any schema.

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 hints at downstream usage by noting lat/lon 'pairs directly with seatgeek_events_near,' but it never states when to call this tool versus alternatives, nor that it should be used to resolve a city before querying events. Usage is only implied.

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