Connect RSS feed bus

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

Annotations already set readOnly=false and destructive=false, indicating a non-destructive write operation. The description adds some context by enumerating scaffold contents (sanitized rows, category maps, refresh policy, adapter source, copyright notes), but it does not disclose side effects, required environment, or return behavior. This partial addition warrants a middle score.

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, concise sentence that front-loads the action and resource, then efficiently lists key components. Every word contributes to the understanding, and there is no wasted verbiage.

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?

With 9 parameters, no output schema, and minimal annotations, the description is too sparse. It does not mention return values, how to observe the created scaffold, prerequisites, or how it fits into the broader system. The lack of this information makes it incomplete for a tool of this complexity.

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 low (22%), so the description must compensate. It hints at parameter meanings through phrases like 'refresh policy' (refresh_interval_sec), 'adapter source' (adapter_url/adapter_mode), and 'category maps' (category_count), but leaves many parameters (active, feed_label, item_count) unexplained. It adds some meaning but not enough for a 9-parameter tool.

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 creates an RSS/Atom/editorial feed scaffold, specifying both the verb (Create) and the resource (feed scaffold). It lists several distinctive features such as sanitized item rows, category maps, and refresh policy, which distinguishes it from other connect_* tools in the sibling list.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions, prerequisites, or context. It simply states what the tool creates, leaving the user without criteria for selecting it.

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