get_all_bills_rss

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

No annotations are provided, so the description carries the full burden. 'Get RSS feed' implies a read-only operation, but the description does not explicitly state that it has no side effects, nor does it disclose caching, format, or authentication behavior.

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 short and front-loads the purpose. However, the 'Returns:' section repeats the first sentence nearly verbatim, adding redundant text without new information.

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 the simple no-param shape and the existence of an output schema, the description covers what the tool does. But in a toolset with several similar RSS siblings, it fails to help an agent choose this one over get_public_bills_rss, get_private_bills_rss, or get_bill_rss.

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 tool takes zero parameters and the input schema is empty. Per the rubric, zero parameters yields a baseline of 4; the description does not need to add 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?

States a specific verb and resource: 'Get RSS feed of all bills.' The scope 'all bills' implicitly distinguishes it from public, private, and per-bill RSS siblings, but it does not name or explicitly contrast with those alternatives.

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?

Provides a generic use condition: 'Use when you want to stay updated on all legislative activity through RSS feeds.' It does not say when to choose this over get_public_bills_rss, get_private_bills_rss, or get_bill_rss, nor does it provide any exclusions.

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