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

Annotations already cover the read-only, open-world, non-destructive profile, and the description goes further with real behavioral nuance: ranks are weighted relative to an entity's own baseline so count does not determine rank, and acceleration is not measured on the guests chart. It also reveals that entries carry slugs and quote episode ids usable for chaining. It stops short of describing response shape or pagination, which keeps it below a 5.

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-loads the purpose, then usage, then the ranking caveat, then chaining targets — a sensible order. It is dense and somewhat long, and the partial re-listing of chart categories duplicates the `chart` enum description, but every paragraph carries distinct 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 six-parameter tool with no output schema, the description covers what an entry contains (rank, movement, reason, quote, playback link, slug), how to follow up on each object type by name, and the ranking edge cases. Nothing an agent needs to select or invoke it correctly is missing.

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 the baseline is 3; the description adds value beyond it by grouping the charts (entertainment, sports, books, guests) and explaining what guests ranks, plus the acceleration caveat affecting `sort`. It repeats a fair amount of what the enum descriptions already say, limiting the upside.

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?

Opens with a specific verb and resource: 'What is trending on podcasts... rank the entities... with movement since the previous edition and why it moved.' The entity types it covers are enumerated and it explicitly distinguishes itself from particle_podcast_get_rankings (Apple/Spotify show charts) and particle_podcast_get_mention_trends.

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?

Explicit when-to-use: call with no arguments for the `all` chart, pick narrower charts by name with groupings listed, `sort=acceleration` for fastest risers. It also states two negative cases with named alternatives, so an agent is routed without reading either schema.

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