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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description adds real value by disclosing the content shape of the returned record and the dual lookup semantics, though it says nothing about size limits or truncation when full text is included.

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 return contents and lookup modes front-loaded; the example is embedded where it is needed and nothing is wasted.

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 no output schema, the description's enumeration of returned fields does the work of explaining the response, and the lookup guidance removes ambiguity about argument combinations. Complete for an agent to call this 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?

Schema coverage is 0%, so the description must compensate, and it does for four of five params: bill_id is a UUID, jurisdiction+identifier form the human bill number path, and session disambiguates. The include_full_text flag is never mentioned, leaving one parameter unexplained.

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 (fetch) and resource (one bill's full record), and enumerates exactly what the record contains: metadata, sponsors, subjects, actions, versions, vote-event summaries. This distinguishes it from siblings like get_vote_details or trace_legislative_history without needing to inspect schemas.

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?

Clearly explains the two lookup paths and when to use each: bill_id for UUIDs, jurisdiction+identifier for human bill numbers, with session to disambiguate. Includes a concrete example (jurisdiction="NC", identifier="HB 123"). Does not name explicit alternatives or exclusions, so short of a 5.

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