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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value beyond that by disclosing the returned field set and the three possible status values, which matters because there is no output schema. It stops short of describing default ordering, whether archived records are excluded by default, or pagination behavior.

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 short sentences with no filler: the field inventory comes first, then the actionable status hint and endpoint. The phrasing is telegraphic rather than fully grammatical, but nothing is wasted and it is easy to scan.

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?

For a nine-parameter, zero-required list tool with no output schema, the description does the important extra work of naming the returned fields and status values. Remaining gaps (default sort order, archived exclusion defaults, paging flow) are partly absorbed by the schema's id_gt/id_lt descriptions, so the definition is close to 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 100%, so all nine filters (id_gt/id_lt paging, update_gt/update_lt, patientId, locationId, practitionerId, include_archived, status) are already documented in the schema. The description adds semantics only for status by tying 'Awaiting Payment' to amounts owed; the other eight parameters gain nothing from the description, so 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?

The description enumerates exactly what a list-invoices call returns (number, dates, patient, totals, status, line items, payment ids) and names the endpoint GET /invoices, so the verb+resource is unambiguous. It does not, however, distinguish itself from the sibling splose_get_invoice (single invoice) or splose_list_payments, leaving that differentiation to the name alone.

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?

One explicit usage rule is given: 'Use status=Awaiting Payment for what is owed.' That is a genuine when-to-use hint, but there is no guidance on when to prefer splose_get_invoice, splose_list_payments, or how paging should be driven, so most selection decisions remain inferred from the tool name.

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