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

Annotations already declare it is a non-read-only, non-destructive, open-world operation, but the description adds real value beyond them: the RSS feed refresh side effect, that it returns every episode with its new number, the per-call confirmation behavior, and the Cotlet API key/auth requirement. This is strong behavioral disclosure for a mutation tool.

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 core capability is front-loaded in the first sentence and the operational details follow logically. The trailing confirmation/API-key sentences are somewhat templated but each still earns its place by disclosing behavior.

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 4-param mutation tool with no output schema, the description covers the return value (every episode with its new number), side effects (RSS refresh), and auth/confirmation requirements. Complete enough for an agent to call correctly, though it never explicitly addresses overwriting existing author/season values.

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, but the description clarifies the numbering enum meaning beyond the schema by explaining that top_to_bottom numbers from the first ID and bottom_to_top from the last. It adds genuine semantic detail about how the numbering order maps to the ID list.

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 set (set author/season, renumber) on a specific resource (many episodes at once) and distinguishes itself from libsyn_update_episode by emphasizing bulk scope and reordering. An agent can tell what this does without opening the schema.

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?

Usage is implied by 'on many episodes at once' versus the single-episode siblings, but there is no explicit when-to-use/when-not guidance or named alternative (e.g. libsyn_update_episode for a single episode). The confirmation note adds context but not tool-selection guidance.

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