Delete RSS feed

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

Annotations already indicate destructive and idempotent behavior, so the bar is lower. The description adds valuable specifics beyond annotations: it stops polling and preserves already-created posts. This gives the agent a more concrete model of the operation's side effects.

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?

Two short sentences, each earning its place: the first states the action precisely, the second adds key behavioral consequences and use context. No filler or redundancy.

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 what is deleted, side effects, and when to use it. Annotations cover destructive and idempotent traits, and no output schema exists, so no return-value explanation is required. Nothing essential 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 only parameter, feedId, is already documented as 'The RSS feed ID to delete.' The description adds 'by ID' but no meaningful semantic detail beyond what the schema provides, so baseline 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 uses a specific verb ('Delete') and resource ('RSS autopost feed by ID'), clearly distinguishing it from sibling tools like create_rss_feed, update_rss_feed, and list_rss_feeds. The subject and scope are immediately unambiguous.

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 explicitly states when to use the tool: when the user wants to stop and remove an RSS autopost feed. It also clarifies that already-created posts are kept, which implicitly distinguishes this from deleting posts. It does not explicitly name alternative sibling tools or when-not conditions, but the guidance is clear enough.

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