itunes_get_top_charts

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

No annotations are provided, so the description carries the full burden. It does not disclose whether this is a read-only operation, any authentication requirements, rate limits, or the structure of the response. It only mentions parameter constraints (default/max for limit), which is minimal behavioral information.

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 compact, with the main purpose stated in the first sentence and parameter details listed succinctly. No redundant information or fluff; every sentence serves a purpose.

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 low-complexity tool with no output schema, the description covers the essential aspects: what it fetches and how to call it. It lacks return format details or extra usage caveats, but given its simplicity, it is reasonably complete, though it could mention that it returns a list of songs or the response shape.

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 schema has no property descriptions (0% coverage), so the description fully compensates. It explains country with examples and the concept of a two-letter code, and limit with its default and maximum. This adds meaningful semantics beyond the bare schema, making both parameters clear.

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 the tool fetches Apple Music's official Daily Top Charts by country, with a specific verb ('Fetch') and resource. It distinguishes itself from sibling tools like itunes_get_new_releases and itunes_get_artist_top_tracks by focusing on top charts vs. other catalog queries.

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 gives clear context on when to use it (to get daily top charts for a country) but does not explicitly mention alternatives or exclusions. The purpose is straightforward enough that an agent can infer when to select it, though explicit guidance about not using it for artist-specific or release-specific queries would be stronger.

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