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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful context that this is a global catalogue rather than a user- or company-scoped list. It does not disclose ordering, response shape, or other behavioral details, but for a simple read-only list the annotations plus context are adequate.

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 sentence that immediately communicates scope and use. It contains no filler, tautology, or repetition of the title/schema.

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 paginated read-only list, the description plus schema covers the essential information: what the tool returns conceptually, how it relates to event workflows, and how to paginate. There is no output schema, but the return shape is reasonably inferable; a note on ordering or exact fields would be a minor enhancement.

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%, with both `page` and `page_size` fully documented including defaults and bounds. The description contributes no additional parameter-level detail, and none is needed given the schema's completeness. Baseline 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 identifies the resource (cities) and frames it as 'the global catalogue of cities', making its listing purpose clear. It also distinguishes it from sibling listing tools by tying it to the `city` field on `event_create`/`event_update` and event display. It does not explicitly state the verb 'list', but the title and 'catalogue' make the intent unambiguous.

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 gives explicit use contexts: selecting a city for event creation/update and showing where events happen. It does not name alternatives or explicitly state when not to use this tool, so it stops short of full routing guidance.

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