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

Beyond the annotations (readOnlyHint, destructiveHint false), the description adds real behavioral context: a plan-tier gate, an API-key access requirement, and the fact that the result is a link rather than inline data. It doesn't cover rate limits or link expiry, but it meaningfully exceeds what structured fields provide.

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 key behavior is front-loaded, but the text is padded: the 'Advanced Plan and higher' requirement is stated twice and the format list is repeated. Tightening would remove a full redundant clause.

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 four well-described params and no output schema, the description supplies the missing return-value picture (zip via link, one file per report) plus the plan gate. A note about link lifetime or cost would complete it, but it is sufficient to call the tool correctly.

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%, so the schema already documents range, format, reports, and show_id enums. The description only echoes the format choices and reinforces multi-report support, adding little beyond the schema. 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 (export) and resource (stats report) and clarifies the distinctive output shape: a download link to a zip with one file per report. An agent can tell it apart from stats-returning siblings like get_show_stats, though no sibling is named explicitly.

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 gives a prerequisite (Advanced Plan or higher) and notes the link can be fetched or piped to the next automation step, but never says when to prefer this over libsyn_get_show_stats or libsyn_get_episode_stats. Usage is implied rather than stated as a when/when-not rule.

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