get_bill

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains meaningful semantics: patrons are grouped by role, and a sessions list with two entries means the bill carried over from the even-year into the odd-year session. It does not mention error cases or authentication, but this is a detail-retrieval tool and the framing strongly implies a safe read operation.

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 compact and front-loaded, with the main purpose in the first sentence. The follow-up notes on patrons and sessions are specific and useful, with no filler or repeated schema information.

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?

An output schema exists, so the description does not need to spell out return values. It supplies the key interpretive details that the schema cannot convey, such as session carryover meaning and patron role grouping. The main gap is parameter guidance, but for a two-parameter getter this is a modest omission.

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 is the only place to explain bill_number and session_code, but it never does. It indirectly refers to 'one bill' and 'session lineage,' but does not explain the expected format of bill_number, what session_code represents, or how the two parameters interact.

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 opens with 'Full detail for one bill' and enumerates the returned fields: title, status, dates, patrons, and session lineage. It clearly distinguishes itself from get_bill_patrons by noting that sibling returns the same patron list with member ids.

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 phrase 'Full detail for one bill' establishes when to use this tool, and the explicit comparison with get_bill_patrons helps route an agent between similar endpoints. It does not exhaustively contrast with other siblings like get_bill_summaries or get_bill_text, but the context is clear enough for typical selection.

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