list_invoices_and_ledgers

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'list all invoices and their associated ledgers'. It does not mention pagination behavior (though schema has page/per_page), whether facility filtering is mandatory, or any authentication or rate limit details. The output schema exists but is not referenced.

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 exceptionally concise: two sentences including a 'Use when' section. It front-loads the main action and wastes no words, making it easy to parse.

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?

Despite having an output schema, the tool has 3 parameters with no schema descriptions and no annotations. The description omits critical context such as how to filter by facility, default pagination limits, or the exact meaning of 'associated ledgers'. The provided usage examples are helpful but insufficient for complete understanding.

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?

The input schema has 0% description coverage, and the tool description adds no information about the parameters (page, per_page, facility_id). It does not explain how to use them or what they control, leaving the agent without guidance.

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 clearly states it lists all invoices and their associated ledgers for the facility. It uses specific verbs ('list') and resources ('invoices' and 'ledgers'), and the scope ('all') distinguishes it from sibling tools like get_ledger or get_ledger_invoices which focus on single or specific ledgers.

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 description provides explicit usage scenarios: 'show me this month's invoices' and 'reconcile billed vs paid', which helps an agent decide when to invoke this tool. However, it does not mention when not to use it or point to alternative tools among the many siblings.

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