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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the exact field set returned, and the deliberate exclusion of payment history and line items. It does not mention pagination mechanics or result limits, but the schema covers those.

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 dense clauses: the operation plus returned fields first, then the exclusion and the alternative tool, then the HTTP path. No filler, nothing repeated from the schema, and the most decision-relevant information is front-loaded.

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?

There is no output schema, and the description compensates by enumerating the returned fields and stating the sort order, which is what an agent most needs for a read-only list. Combined with 100% schema coverage for the 8 input parameters, the definition is close to self-sufficient; pagination response shape (next_page.before_id) is only implied via the schema.

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 100%, with every parameter (limit, cursors, record_ids, payment_status, practitioner_ids, date bounds) documented inline, so the schema does the heavy lifting. The description adds no parameter-level meaning — it never mentions the available filters or the cursor convention — so the baseline 3 is appropriate.

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 ('List client invoices') plus the sort order ('newest first'), and enumerates the fields returned (number, date, totals, amount due/paid, status, client, practitioner). It also explicitly separates itself from practice_better_get_invoice, so an agent can distinguish this list tool from its detail sibling without opening either schema.

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 a clear when-not condition ('Payment history and line items are not in the list') and names the alternative tool to use instead (practice_better_get_invoice). However, it offers no guidance on the filter dimensions the tool exposes (payment_status, record_ids, date ranges) or when a filtered list is preferable to an unfiltered one, so routing is covered but selection strategy is not.

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