qui_remove_rss_rule

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

The description adds no behavioral information beyond the destructiveHint annotation. It does not mention permanence, permissions, side effects, or what exactly gets destroyed. Since the annotation already signals destructiveness, the description provides no additional context.

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 a single sentence that directly states the endpoint and parameter-passing conventions. It is front-loaded with the action and contains no extraneous words.

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 deletion tool, the description covers the endpoint and parameter structure, but omits explicit mention of required path variables, whether query/body are needed, and any prerequisites or error scenarios. The output schema may address return values, but usage context remains incomplete.

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?

With 0% schema description coverage, the description compensates by explaining how to pass path variables, query values, and body within the arguments object. However, it does not specify the exact keys (instanceID, ruleName) or expected query/body content, leaving significant room for ambiguity.

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 clearly states it calls a DELETE endpoint for RSS rules, unambiguously indicating removal of a specific rule. It distinguishes from sibling tools like qui_get_rss_rules and qui_rename_rss_rule by focusing on deletion.

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 implies usage via the DELETE method, but provides no explicit when-to-use guidance or exclusions. It does not mention alternative tools or conditions under which this tool should be selected, leaving the agent to infer based on the name and endpoint.

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