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

Annotations already declare readOnly/openWorld/idempotent, so safety is covered; the description adds the non-obvious behavior that large dossiers degrade to an outline with a continuation offset, and that nested records within stages are preserved intact. It does not mention permission scope or whether the outline call is itself counted against limits, so it stops short of full disclosure.

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 dense sentences with the core action front-loaded and no filler. "Stages preserve nested records whole" is compressed to the point of being slightly cryptic for a first-time caller.

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 an output schema present, return values need no explanation, and the overflow/outline workflow is the main thing an agent must know before calling. The remaining gap is how section names are shaped and what the notice on oversized limits looks like, but overall it is sufficient to invoke 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 100%, so the baseline is 3; the description earns extra by explaining that an omitted session means the verified current official session and that section must come from the returned outline. billCode provenance from canparl_search_bills is also reinforced, though the limit/offset semantics stay with the schema.

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 ("Read one House or Senate bill's official dossier"), bounded to a single bill, which cleanly separates it from canparl_search_bills and the other retrieval siblings. An agent knows immediately what this tool returns.

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 explicit procedural routing: obtain billCode and session from canparl_search_bills, and when the dossier is large, re-call with a single section from the outline and follow pagination.nextOffset. The conditional path for oversized results is spelled out rather than left to inference.

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