Outstanding client balances

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

With no annotations, the description carries the full behavioral burden. It does disclose the shape of the returned data, but says nothing about pagination (despite a page_token parameter), whether results are scoped to all clients or a filtered subset, what permissions are needed, or how 'outstanding' is determined.

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?

One compact sentence, front-loaded with the verb and resource, and every clause adds information about the returned fields. It is a sentence fragment rather than prose, but there is no waste.

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?

No output schema or annotations exist, so the description must stand alone; it covers the returned fields but omits pagination, scope, and permissions for a two-parameter list tool. Adequate for the core purpose, incomplete for correct invocation.

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% for both parameters, so the description would need to compensate — and it does not mention limit or page_token at all. The agent gets no clue about page size caps, pagination semantics, or what happens when the result set exceeds one page.

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 states a specific verb and resource — 'Lists clients with outstanding bills' — and enumerates the returned fields (total owed, last payment, newest due date, outstanding bills), so the agent knows exactly what the tool produces. It does not explicitly contrast itself with close siblings like clio_bills_list or clio_billable_matters_list, which keeps it below a 5.

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 exclusions, and no named alternative. An agent must infer from the word 'outstanding' alone that this is the A/R aging view rather than the general clio_bills_list, and nothing tells it which to prefer.

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