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

Annotations already establish read-only, non-destructive, open-world behavior, so the description's job is to add context — which it does by disclosing that the no-slug call returns counts and that the slug call returns topic detail plus a sample of raw subject names folded in. It does not mention pagination behavior beyond max_items or ordering of results, which keeps it from a 5.

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?

Three tight sentences with the core description front-loaded, followed by the usage guidance and then the hand-off to search_bills. No filler or restated name/title.

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?

There is no output schema, so the description must convey return values — and it does for both modes (taxonomy with bill counts; slug detail with raw subject sample). For a two-parameter read-only tool with full schema coverage, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the behavioral consequence of passing a slug (detail plus sample raw subjects) versus omitting it (whole taxonomy), which the schema only states neutrally. It says nothing extra about max_items, capping the score at 4.

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 resource (canonical topic taxonomy with per-topic bill counts) plus the backing endpoint, and explicitly explains the two modes (list vs. single-slug detail). It also distinguishes itself from search_bills, so an agent can place it in the toolset without opening the schema.

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?

Gives an explicit when: 'Call this first to find the right slug ... instead of guessing one.' It also names the alternative and the condition for choosing it: to get actual bills, use search_bills with topic=<slug>. Both the use case and the hand-off are spelled out.

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