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

With no annotations provided, the description carries the full burden. It transparently discloses that the tool does not return bill rows itself, explains the topic structure (title/subject membership rule tuned for precision over recall), and mentions the presence of live bill_count and how_to_fetch_bills. This is rich behavioral context beyond a simple 'list topics' definition.

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 well-structured and front-loaded: it starts with the core action, lists examples, explains the tool's purpose, and ends with a critical pairing note. Every sentence adds value, and the length is appropriate for the tool's complexity.

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 zero-parameter tool with no output schema, the description is remarkably complete. It describes what the topics are, provides examples, notes the precision-over-recall tuning, and explicitly states what the tool does not do (return bills) while pointing to alternatives. This fully equips the agent to invoke the tool correctly.

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 has zero parameters, so the description doesn't need to explain parameter semantics. The baseline of 4 applies, and the description clearly explains what the tool does, which is sufficient for a parameterless 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 the action (List), the resource (curated cross-state topic trackers), and includes concrete examples. It explicitly distinguishes itself from sibling tools by noting it does not return bill rows and pointing to search_legislation for that purpose.

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 explicit guidance on when to use this tool: as the entry point for discovering what subjects Bill Commons tracks and how to get bills in one. It also tells the user to pair it with search_legislation or the REST API's /topics/{slug} for actual bills, offering clear alternatives.

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