apple_podcasts_charts

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

No annotations provided, so description carries the burden. It explains it returns chart rankings from public feeds, which is transparent. However, it does not disclose rate limits, caching, or data freshness. For a simple chart retrieval, this is adequate but not thorough.

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?

Three sentences with no fluff. Front-loaded with the core purpose. 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 chart retrieval tool with no output schema, the description is complete: it specifies source, supported collections, and parameter context. Could optionally mention output format, but not necessary.

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 parameter descriptions. The description adds value by listing supported collections explicitly, which goes beyond the schema's generic 'Chart collection' description. Other parameters are standard and well-described in 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?

The description clearly states it retrieves Apple Podcasts chart rankings from public iTunes RSS JSON feeds, and specifies supported collections (`toppodcasts`, `topaudiopodcasts`). This distinguishes it from sibling tools like searches or show-specific tools.

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 implies usage for chart rankings but does not explicitly guide when to use this tool versus other Apple Podcasts tools (e.g., search, show details). No exclusions or alternatives are mentioned.

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