qui_rss

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

No annotations exist, so the description must carry the behavioral burden. It partially does by exposing HTTP methods (GET vs POST/PUT/DELETE), which indicate read vs mutating operations, and by showing exact endpoint templates. It does not disclose side effects, permission needs, reversibility, or error behavior for the mutations.

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 efficiently organized: a concise usage instruction followed by a clear bulleted list of 14 operations with endpoints. The list is long but necessary for a dispatcher tool, and the format is scannable. A plain-language gloss per operation would improve it, but current structure earns its place.

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?

The tool has an output schema, so return values are covered elsewhere. The description provides a complete operation inventory, HTTP methods, and path/query/body conventions, which is substantial for a dispatcher. It is slightly incomplete due to missing per-operation purpose details or permission/error context, but adequate for basic selection.

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 0%, but the description compensates somewhat by explaining the structure of the free-form arguments object, including path variables, query params, and body. It does not enumerate operation-specific parameters beyond endpoint path variables, so the agent still lacks detailed per-operation parameter semantics.

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 the tool is for "qui rss operations on qui" and enumerates all operations with HTTP endpoints, making the RSS domain and actions (add, get, remove, rename, etc.) explicit. It differentiates from sibling tools by focusing exclusively on RSS operations, though the broad dispatcher form makes it slightly less sharp than a single verb+resource description.

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 gives concrete invocation guidance: "Pass `operation` and an `arguments` object; path variables go directly in arguments, query values in arguments.params, and a JSON request body in arguments.body." However, it does not explicitly state when to prefer qui_rss over sibling tools or how to choose among the listed operations beyond their names and endpoints.

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