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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known, and the description goes further by specifying exactly what is destroyed (the feed binding and its seen-items history) and exactly what survives (published, queued, and pending-approval posts). That preservation detail is the non-obvious fact an agent needs before calling a destructive tool, and it is not recoverable from any structured field.

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 short sentences with zero filler: the action and its effect first, the retention caveat second, the id-sourcing hint last. Each sentence carries distinct information and the most consequential fact (posts are kept) is not buried.

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 single-parameter destructive tool with no output schema, this covers everything an agent needs: what is removed, what is preserved, the follow-up tool for the preserved data, and where the id comes from. Annotations carry the safety metadata, so no behavioral gap remains.

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% and the single parameter already carries the description 'The feed id from list_feeds', which the prose merely restates. No additional format, validation, or sourcing nuance is added 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 and resource ('Stop turning a feed into posts') plus the hidden side effect ('forget which items it has seen'), which is more precise than the title's 'Remove an RSS feed'. It also distinguishes itself from delete_post in the same sentence, so an agent can separate feed-level removal from post-level deletion 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 routing guidance for the adjacent task: existing posts are kept, and 'delete those separately with delete_post if needed' names the alternative and the condition that selects it. It also tells the agent how to obtain the required id ('Get the feed id from list_feeds'). It stops short of stating exclusions such as whether a removed feed can be re-added or what happens to in-flight fetches, so it is strong but not exhaustive.

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