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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint, so safety is covered. The description adds a genuinely useful auth requirement (needs the Cotlet API key with access to this app), but repeats 'Read only' redundantly and says nothing about pagination or response shape.

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?

Front-loaded and readable, but the ranking-by-trackers/fan-requests idea is stated twice (first and third sentences), which is wasted space in a four-sentence description. Trimming the repetition would tighten it without losing information.

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 read-only lookup with no output schema, the description conveys what is returned (your top locations ranked two ways) and the auth requirement, and annotations cover the safety profile. Return format is unspecified, but that is acceptable given no output schema is defined.

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 100%, so baseline is 3, but the description goes further by disambiguating the enum values: trackers = followers, fan_requests = fans asking you to play there. That adds meaning beyond the bare enum, though limit and artist_id are left entirely to the schema.

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?

Clear verb+resource: it returns the artist's top locations ranked by trackers or fan requests, and pins the concept to 'Top Markets' from Insights. It differentiates from siblings like get_follower_stats by being a geo-ranked list, though it doesn't explicitly name the sibling it might be confused with. Purpose is 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?

Implies usage (pull your top markets to prioritize touring) and states the two ranking modes, but gives no explicit when-to-use vs alternatives such as get_follower_stats or get_event_stats. No exclusions or preconditions beyond the general auth note.

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