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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the full safety profile is covered by structured data. The description adds nothing behavioral beyond that — no indication of whether the city set is static or grows, whether entries refresh, or any rate/size limits — though for a fixed-catalog read there is little behavior left to disclose.

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?

A single sentence that front-loads the resource and then specifies the payload contents; every clause carries information and none is redundant. No boilerplate, no padding.

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?

With no output schema, describing the shape of each returned entry (site, MCP endpoint, event count) is the key missing piece and the description supplies it. Annotations cover safety, and there are no parameters, so the remaining gap is minor: it never states that returned cities are the valid inputs for the sibling search tools.

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 and the description correctly does not invent any. Nothing in the schema needs further explanation, and there is no risk of misusing input.

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 names the specific resource (the cities the service covers) and enumerates what each entry contains: site, MCP endpoint, and indexed event count. That is well beyond a tautology and lets an agent distinguish this catalog tool from the event-oriented siblings (get_event, list_upcoming, search_events). It loses a point only because the operation is expressed as a noun phrase rather than a verb, leaving 'list' to be inferred from the title.

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?

There is no statement of when to call this versus search_across_cities, list_upcoming, or the other siblings, and no mention that this is the natural discovery step for obtaining valid city identifiers. The usage context is inferable but never stated, and no exclusions are given.

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