Bill detail including line items

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

With no annotations, the description carries the full behavioral burden. It helpfully implies a read-only fetch and discloses the return shape (line-item fields plus optional pre-rendered HTML), which is real added value given there is no output schema. However, it says nothing about permissions/authentication, error behavior for an invalid bill_id, or whether the HTML is expensive to generate.

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?

Two tight sentences with the core return content front-loaded and the optional HTML mentioned last. Every clause earns its place; nothing is redundant with the schema.

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?

Because no output schema exists, the description usefully sketches the return payload (date, description, quantity, price, total, time-entry link), which is exactly what the agent needs. It remains thin on how bill_id is sourced and on error/permission behavior, so it is not fully complete.

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. It explains include_html meaningfully ('Optionally also the pre-rendered HTML of the bill'), which resolves the only non-obvious parameter, but bill_id is left entirely to inference. One of two parameters is covered, so this is partially compensating.

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 ('Returns the bill detail and its line items') and even enumerates the line-item fields, so the agent knows exactly what comes back. It does not explicitly distinguish itself from the sibling clio_bills_list (list vs. single fetch) or clio_line_item_update, leaving that separation implicit.

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?

There is no when-to-use guidance, no mention of how to obtain the required bill_id (presumably from clio_bills_list), and no exclusions relative to siblings like clio_bills_list or clio_outstanding_balances. The agent must infer the retrieval workflow from the name alone.

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