get_bill_text

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

With no annotations, the description carries full behavioral burden and does so thoroughly. It discloses HTML stripping, default-to-most-recent-version, 15,000-character truncation with a 'truncated' flag, and flattening of amendment markup. These are meaningful behaviors an agent would otherwise not know.

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?

Compact and well-structured: the core purpose leads, followed by parameter guidance, return behavior, and formatting nuances. Every sentence earns its place with no filler or repetition of schema data.

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 tool's moderate complexity, no annotations, and no output schema, the description covers the essential return behaviors: full text, truncation, truncated flag, and amendment handling. It is missing only minor details like response envelope or error cases, which are not critical for selecting and invoking 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?

Schema description coverage is 0%, so the description must compensate. It adds useful semantics and examples for document_code, but says nothing about bill_number or session_code beyond their schema titles. Two of the three parameters remain underexplained, leaving a notable gap.

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: retrieving the full plain-text content of a single bill version. The phrase 'one bill version' distinguishes it from bill metadata, summaries, history, and votes among siblings. It also clarifies the HTML-to-plain-text transformation, making the tool's core purpose unmistakable.

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 clear context on how to select a version and the default behavior, but does not explicitly contrast with sibling tools like get_bill, get_bill_summaries, or get_bill_history. The intended use is implied by 'Full text' rather than explicitly stated as when-to-use versus alternatives.

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