get_geo_top_artists

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. However, the description adds no behavioral context beyond the annotations—no mention of pagination behavior, auth requirements, rate limits, error cases, or result ordering. With annotations present, the bar is lower, but the description still provides zero additional behavioral insight.

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 three short sentences plus an argument list, with no wasted words. It front-loads the core purpose and then gives per-parameter explanations. Every sentence earns its place.

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 read-only tool with an output schema and strong annotations, the description covers the essential aspects: purpose and parameter semantics. It does not explain any prerequisites or edge cases, but these are less critical given the low complexity and existing structured metadata.

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 0%, so the description must compensate. It does: country is explained as 'Country name in ISO 3166-1 form, such as Finland,' and limit/page are defined as 'Results per page' and 'Which page of results to fetch.' This adds meaningful guidance beyond the bare schema types and defaults.

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 clearly states a specific verb and resource: 'Get the most popular artists in one country.' This differentiates it from sibling tools like get_geo_top_tracks (tracks vs artists), get_chart_top_artists (global chart vs country), and get_tag_top_artists (tag-based vs geo-based).

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 provides no guidance on when to use this tool versus alternatives such as get_chart_top_artists or get_user_top_artists. It only implicitly suggests country-based use, but does not explicitly name any sibling or condition for choosing it.

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