simplepractice_list_billing_items

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds non-obvious behavior beyond that: that an empty result is a legitimate answer rather than an error, and that paging is cursor-based with nextCursor fed back as 'before'. It stops short of describing the shape of returned records, but that is partly delegated to the view parameter.

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?

Three compact sentences, front-loaded with what is returned and followed by the two most operationally important caveats (empty-is-valid, cursor paging). No filler, though the paging sentence is slightly terse relative to the ambiguity of the 'before' name.

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 read-only, zero-required-parameter list tool with no output schema, the description covers the resource, the empty-result case, and pagination, and the enums are documented in the schema. What an agent needs to call it correctly is essentially present; only return-shape and sibling selection are unaddressed.

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?

With only 50% schema description coverage, the description compensates meaningfully: it enumerates the kind values informally and explains the 'before' cursor's provenance (the returned nextCursor from a previous call), which the schema only names. pageSize and view semantics remain schema-only, keeping it below a 5.

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 first sentence names the specific resources (invoices, statements, superbills, receipts, account history) and scopes them to the Client Portal, so an agent knows exactly what record type it retrieves. It lacks an explicit verb like 'list' and does not name sibling tools such as get_billing_overview, but the resource plus portal scope is distinctive enough to separate it from the other billing sibling.

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?

It gives real interpretive guidance — an empty list is valid, and many practices bill entirely outside the portal — plus how to page. However, it never states when to choose this over get_billing_overview or get_account, and no exclusions or prerequisites are given, so routing is left to inference.

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