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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context: the fixed upstream source, the exact fields in a row (place, movement since yesterday, artist, genres, platform figures with read dates, profile link) and the 25-place ceiling.

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 purpose and source are front-loaded in the first clause, and every English clause adds information. The full Polish restatement duplicates the same content and costs space without adding guidance, which keeps it short of a 5.

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 an output schema present and annotations covering safety, the description supplies what is still needed: source of truth, row fields, and result ceiling. Only the freshness semantics of 'movement since yesterday' (how often the chart updates) and behavior for an unknown genre slug are left unaddressed.

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%, with both genre and limit fully documented including range and default, so the schema carries the burden. The description only restates the optional genre filter and the 25-place limit without adding syntax, slug examples or fallback behavior beyond 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?

States a specific resource (the TopAI chart of Polish AI music on TopAIMuza.pl) and even names the canonical page it mirrors, plus the fields returned. It is unmistakably different from siblings such as get_artist, search_tracks, list_genres and new_releases.

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 optional genre filter and the 25-place cap imply how to scope a query, but nothing states when to pick this over search_tracks or new_releases, nor any exclusion. Usage is only inferable from the purpose statement.

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