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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does so by disclosing the return content (counts of approved conventions) and confirming the call is argument-free, which is useful preparatory information for an agent building a filter call.

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 tight sentences: the first front-loads what is returned, the second gives the actionable usage. No filler, and the most decision-relevant information comes first.

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, the description must carry the return-value burden, and it names the key fields (regions, states/provinces, metros, approved-convention counts). It doesn't describe the response structure (flat list vs. nested by region), leaving a small gap for a lookup 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?

The tool takes zero parameters, so the baseline is 4. The description reinforces this with 'Takes no arguments,' eliminating any doubt an agent might have about optional filters.

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?

Identifies the exact resource returned: regions, states/provinces, and metro areas tracked by ArtistAlly, with approved-convention counts. This is immediately distinguishable from the sibling tools (get_convention, search_conventions, list_open_registrations), which operate on individual conventions rather than the coverage map.

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?

Explicitly states the use case: 'Use it to learn valid region/state/metro filter values for the other tools,' which tells the agent to call this before filtering elsewhere. It stops short of naming a specific sibling or describing when it can be skipped, keeping it at a 4 rather than a 5.

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