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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's added value is the disclosure that entities are decoded and that texts over 40,000 characters are clipped with a '[truncated]' marker. That truncation caveat is a real behavioral trait an agent must know before quoting, and it is not expressed in any structured field.

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: what it returns, how to obtain the ID, and the one truncation caveat. The critical constraint is placed last but only after the core definition is front-loaded; 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?

There is no output schema, and the description compensates by characterizing the return as decoded plain text suitable for quoting and by flagging the truncation marker. Minor gaps remain — it doesn't say what happens for an invalid or missing text_id, or whether the response is a bare string — but nothing essential to invoking 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?

With a single parameter at 100% schema description coverage, the schema already documents text_id and the description repeats the same provenance hint. The parenthetical about each version having a date and type adds marginal context for choosing a version but not for the parameter's format itself, so this lands at the baseline.

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 — the cleaned plain text of one bill-text version — plus the underlying endpoint GET /v1/texts/{text_id}. It implicitly distinguishes itself from siblings like get_bill_text_history (versions) and get_bill_diff (comparison) by scoping to a single version's rendered text.

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 concrete guidance on where the required text_id comes from (get_bill with include:['texts'], noting each version carries a date and type). It does not explicitly name sibling alternatives such as get_bill_text_history when the agent wants the list of versions rather than text, so it stops short of full routing guidance.

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