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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that only cities with published profiles appear and that counts are included, but says nothing about ordering, pagination, or how min_artists changes the result set.

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 short sentences with the core scope stated first and the filtering option second; no filler. It is terse to the point of omitting parameter detail, but not bloated.

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 small read-only list tool with no output schema, the description conveys what the rows represent and that counts are returned. It falls short on the min_artists threshold and on result ordering/limits, which an agent would need to use the tool precisely.

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 50%: 'query' is described only as 'part of the city name', and the description clarifies it as a prefix match ('начало названия'), which is a real semantic addition. However, min_artists has no description anywhere and the text only vaguely alludes to profile counts, so the second parameter remains undocumented.

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 resource (cities) and the exact subset returned: cities that have published profiles, together with the profile count. That is specific enough to separate it from search_artists or list_categories, though it never explicitly contrasts itself with those siblings.

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?

It states that results can be narrowed by the start of a city name, which implies a browsing/autocomplete use case, but gives no explicit when-to-use versus search_artists or list_categories, and no exclusions or prerequisites.

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