get_private_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 behavioral burden, and it discloses almost nothing: no auth requirements, rate limits, caching, or update cadence. The only behavioral trait conveyed is the content scope (private bills), which is thin for a tool with zero structured behavioral hints.

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 scoping sentence is front-loaded and useful, but the 'Returns: RSS feed of private bills' block is redundant with the output schema and restates 'private bills' for the third time. Minor trimming would improve it.

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 no-param read-only feed with an output schema, the description is close to sufficient, but it never explicitly routes the agent away from get_public_bills_rss and get_all_bills_rss. In a sibling set this dense, that missing distinction leaves a real selection gap.

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 no parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No parameter-level gaps exist.

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 (Get) and resource (RSS feed of private bills), and the word 'only' scopes it against the public/all-bills RSS siblings. It stops short of naming those siblings (get_public_bills_rss, get_all_bills_rss), so the differentiation is implied rather than explicit.

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?

'Use when you want to monitor private member bills and private bills through RSS feeds' gives a plausible use case but no when-not condition and no named alternative. An agent choosing among the four RSS siblings gets only the word 'only' as routing guidance.

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