qui_set_rss_rule

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It does reveal that this is an HTTP POST (implying a mutation) and explains how to structure arguments, but it does not disclose the actual side effects, whether the operation is idempotent, required permissions, or the nature of the request body. Significant behavioral ambiguity remains.

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, focused sentence that front-loads the endpoint and then succinctly explains the argument convention. Every word earns its place, and there is no redundant content or restatement of the name.

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?

Given that this is a relatively complex endpoint call with path, query, and body components, and no annotations, the description is incomplete. It omits the actual path variables beyond {instanceID}, any query parameters, the expected request body shape, and the business context. The presence of an output schema mitigates the need to describe return values, but the lack of request guidance makes the tool hard to invoke correctly without external API knowledge.

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 input schema is nearly bare (only a generic 'arguments' property with no documented fields), so the description must compensate. It does provide meaningful structure: path variables go directly in arguments, query values in arguments.params, and the request body in arguments.body. This is genuinely useful for an agent facing an untyped schema, even though it does not enumerate the specific variables or body fields.

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 the HTTP operation and endpoint ('Call qui's POST /instances/{instanceID}/rss/rules endpoint') but fails to explain the semantic purpose of the tool—does it create, update, or configure an RSS rule? It reads as an implementation instruction rather than a clear statement of what the tool does, and it does not differentiate from related sibling tools like qui_rename_rss_rule or qui_get_rss_rules.

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?

No guidance is provided about when to use this tool versus alternatives. The description focuses solely on argument-passing mechanics and never mentions scenarios, prerequisites, or exclusions. An agent receives no contextual help in deciding between qui_set_rss_rule and other RSS rule operations.

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