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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses two important side effects: it stops polling and preserves already-created posts. This clarifies what is destroyed and what survives, which is exactly the kind of context that helps an agent set expectations. No contradictions with annotations.

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 description is three short sentences, each with a distinct job: state the operation, state the side effect, state the intended use. There is no redundant or promotional language, and the key verb and object are front-loaded.

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 delete operation, the description covers the action, the side effect on related posts, and when to use it. The annotations already provide destructive and idempotent hints, and the schema fully documents feedId. Nothing critical is missing for an agent 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?

The only parameter, feedId, is already fully documented in the schema with 'The RSS feed ID to delete,' so the description does not need to add more. The phrase 'by ID' in the description simply mirrors the schema without adding new format or constraint details. At 100% schema coverage, the baseline of 3 is appropriate.

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?

The description states a specific action ('Delete'), a precise resource ('RSS autopost feed'), and the input method ('by ID'). It also adds scope by noting that polling stops and already-created posts are kept, which distinguishes it from deleting posts, media, or schedules. This is more specific than the title and differentiates it from sibling tools like update_rss_feed.

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?

The description includes an explicit usage condition: 'Use this when the user wants to stop and remove an RSS autopost feed.' This tells an agent when to invoke it with confidence. It does not name alternative tools for related scenarios (e.g., pausing without deletion), so the guidance is clear but not exhaustive.

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