simplepractice_list_billing_items

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

Beyond the minimal isSearch/systemOnly annotations, the description discloses two non-obvious behaviors: empty results are meaningful rather than errors, and pagination uses a nextCursor that must be passed as 'before'. This is useful behavioral context that annotations do not provide.

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 short sentences, each carrying essential information: what the tool returns, the empty-list caveat, and pagination mechanics. No filler or repetition.

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?

The description covers the core list behavior, empty results, and pagination intent, which is strong for a simple two-parameter tool. However, the cursor instruction cannot be satisfied with the given input schema, and because there is no output schema the description remains the only source for return expectations. That gap prevents it from being fully 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?

The prose restates the kind enum values and adds portal context, but the schema already supplies those enums with far better precision. More importantly, the pagination instruction references a 'before' parameter that is absent from the input schema, so an agent following the description cannot actually execute pagination. The view parameter is only documented by the schema, not enhanced by the description.

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 enumerates the resource scope: invoices, statements, superbills, receipts, or account history from the Client Portal. It is distinguishable from sibling list tools like appointments and documents, though it does not explicitly name the alternative or state the verb 'list'.

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 gives important operational context: an empty list is a legitimate answer because many practices bill outside the portal, and it explains cursor pagination. However, it does not state when to prefer this tool over alternatives or provide exclusions.

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