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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read only' is redundant. However, the description adds a genuine behavioral detail beyond the annotations: it requires the user's Cotlet API key with access to the app, which is material for a read call that may fail on auth.

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 opening fragment restates the title, and the second sentence largely repeats the first ('first 7, 30 and 90 days, all time'), so there is measurable redundancy. The auth note and the daily/range_total explanation do earn their place, but the front matter is padded.

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 no output schema, the description does the work of explaining return content (windows and per-day breakdown) and auth needs, which is adequate for a single-episode stats tool with fully covered parameters. The unexplained 'daily'/'range_total' references leave a small gap.

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 schema already documents metric, start_date, end_date and episode_id, making 3 the baseline. The description references 'daily' and 'range_total' which don't map to any schema parameter, adding minor confusion rather than clarifying the documented fields.

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 verb+resource (returns download stats) and precisely scopes it to 'one episode,' which naturally distinguishes it from libsyn_get_show_stats (show-level) and libsyn_get_downloads_breakdown. It also enumerates the returned windows (7/30/90 days, all time, per day), so an agent knows exactly what the call yields.

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?

It hints at a use case ('so episodes of different age compare fairly') and describes metric options, but never says when to pick this over the sibling stats tools or what prerequisites/exclusions apply. Usage is implied rather than stated.

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