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 largely redundant. The description does add genuinely useful context the annotations do not carry: the API-key auth requirement with app access, and that the metric defaults to IAB (which affects what the numbers mean). It does not describe response shape or date-range limits.

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-loaded with the resource and breakdown, but the second sentence re-states the first almost verbatim ('all time, this week, this month and per day for the range you choose'), which is pure redundancy. Authentication and metric notes do earn their 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 an all-optional, fully documented 4-parameter read tool with no output schema, the description covers the returned breakdown (all-time/week/month/per-day), the default metric, and the auth prerequisite. Only date-range bounds or per-episode contrast are missing, which is minor.

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 description coverage is 100% and the schema already documents metric, show_id, and both dates with defaults. The description's 'metric is IAB downloads by default, or unique downloads' merely restates the enum and adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 (get) plus resource (show stats) and scopes it clearly as whole-show downloads broken down all-time/week/month/per-day. It implies the distinction from libsyn_get_episode_stats by saying 'for the whole show,' but never names an alternative, so sibling differentiation is left to inference.

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 phrase 'Returns downloads for the whole show' implies when to prefer this over per-episode stats, but there is no explicit when-to-use statement, no when-not, and no mention of libsyn_get_downloads_breakdown or libsyn_export_stats_report as alternatives.

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