qbittorrent_rss_matching_articles

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

The readOnlyHint annotation already signals safe read behavior. The description adds the return format ({feed name: [article titles]}) which is useful, but it does not disclose edge cases such as behavior for nonexistent rule names or empty results. This matches the baseline for annotated read operations.

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, front-loaded sentence that states the purpose and output format. Every word contributes value with no filler or repetition of schema or annotation details.

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 simple single-parameter read-only tool with an output schema, the description provides the essential behavior and return structure. It is sufficient for an agent to infer the tool's role, though it lacks explicit mention of edge cases or parameter constraints.

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 has 0% description coverage for the only parameter, rule_name. The description only references 'a rule' without clarifying the exact semantics (e.g., whether it must match an existing rule name, case sensitivity, or how rule names are defined). It does not compensate for the missing schema documentation.

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 returns all feed articles matching a rule, with a specific output format of {feed name: [article titles]}. This distinguishes it from sibling tools like qbittorrent_rss_items by scoping to rule matching and specifying the result structure.

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 purpose implies when to use this tool (to see articles matched by a rule), but it does not explicitly mention alternatives or exclusions. No guidance is given comparing it to rss_items or other RSS tools, so usage context is only implied.

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