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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: the call is queued rather than synchronous, the effect is visible later in get_podcast_profile, and the latency is normally minutes. It does not cover auth/permission needs, keeping it short of a 5.

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?

Three tight sentences: the action first, then the outcome and timing, then the scope exclusion. No filler, and each sentence carries distinct information (purpose, result/latency, boundary).

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 supplies what an agent needs: it states that the call returns the show's current state and the queue timestamp, and explains where subsequent episode changes surface. For a simple one-parameter, read-only, idempotent tool, nothing material is missing.

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 single id parameter is thoroughly documented there (show_id from find_podcast_contacts, RSS URL, or podcast:guid). The description only alludes to 'one podcast's RSS feed' and adds no format or constraint 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 action (re-read one podcast's RSS feed now instead of at the next scheduled check) with clear scope and actor ('Ask for...'). It also distinguishes itself from siblings by naming get_podcast_profile as where results land and clarifying that contact routes are handled elsewhere, so an agent can separate it from find_podcast_contacts or get_podcast_profile without opening a 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?

Gives clear context for when to call it: to force an immediate feed read rather than waiting for the scheduled check, with the expected payoff explained (new episodes appear within minutes). It also states a boundary ('contact routes are re-checked separately, not by this call'), though it does not name the alternative tool explicitly, so the routing hint is implicit rather than spelled out.

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