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

Annotations already cover the safety profile (readOnlyHint=true), so the description earns credit by adding what annotations cannot: it is free, requires no API key, and is rate-limited to 10 requests per minute — all decision-relevant for an agent. It stops short of describing failure modes (private/dead feeds, unsupported link types), which keeps it out of the top band.

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?

One compact sentence that front-loads the input contract (what URL forms are accepted) before the output contract (episode list, indexed status, transcription pricing) and the operational facts (free, no key, 10/min). No filler.

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 carries the return-value burden and does so at a high level — episodes, which are already indexed, price for the rest — plus auth and rate-limit facts. Gaps are modest: no mention of error behavior for invalid, private, or oversized feeds, and no hint about result size for very large feeds.

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 0% and the single parameter is merely typed as a URI, so the description is the only source of meaning — and it delivers it by stating the url may be a public RSS feed or an Apple/Spotify link, telling the agent which input forms are accepted. It omits examples or format specifics for Apple/Spotify links.

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 and resource: reads a public RSS/Apple/Spotify feed and returns its episodes annotated with what is already indexed on Podgist plus transcription prices. This is clearly distinguishable from get_podcast/list_episodes (existing catalog reads) and from quote_* tools, though it does not name those siblings 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?

Usage is implied rather than stated: the free/no-key framing and the 'price to transcribe the rest' output suggest calling this before quote_index/checkout_quote, but the description never says when to prefer it over get_podcast, find_podcasts, or quote_episode, nor any exclusion conditions.

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