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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior context (what fields come back, that amounts are in the practice currency), but omits sort order, default range behavior, and total/result limits for an open-world list.

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 sentences, both front-loaded with the highest-value information: scope first, then filters, then the currency caveat. No filler or redundancy.

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?

With no output schema, the description usefully discloses the return shape (patient, totals, outstanding). For a six-parameter paginated list it is nearly complete, but the default behavior when no date range is supplied is left unexplained.

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 100%, so the baseline is 3. The description contributes one real clarification — that the start/end filters apply to the invoice date specifically — but otherwise restates the status and paid_or_outstanding enums without adding meaning beyond the schema.

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 names a specific verb+resource (list invoices), defines the scoping dimension (invoice date within a range), and previews the returned fields (patient, totals, outstanding). It is clearly distinct from the singular semble_get_invoice sibling, though it never names that sibling explicitly.

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?

Usage is implied by the filter dimensions mentioned (status, paid_or_outstanding), but the description never says when to use this list versus semble_get_invoice or semble_list_patient_bookings. It also doesn't say what happens when start/end are omitted, which matters since all six parameters are optional.

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