simplepractice_list_billing_items

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

The annotation readOnlyHint=true already marks the tool as non-destructive. The description adds value beyond this by noting empty lists are a legitimate response (many practices bill externally) and by documenting cursor-based pagination. Together, these give a clear behavioral profile.

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 carry all essential information: the resource scope, the empty-list nuance, and the pagination mechanism. Nothing is wasted, and the most important info 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?

For a list tool with no output schema, the description covers pagination, edge cases, and scope. It does not describe the item shape or error handling, but the core calling contract is clear and complete given the simplicity of the operation.

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 only 33% (only 'before' has a description), so the description must compensate. It does: the opening list covers 'kind' values, and it explains the 'before' cursor semantics. 'pageSize' remains trivial but is well defined by schema defaults and max.

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 states it lists invoices, statements, superbills, receipts, or account history from the Client Portal. It names the specific resource and action, which distinguishes the tool from siblings like list_payment_methods or get_billing_overview, though it does not explicitly name them.

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 provides practical usage guidance: it assures empty lists are valid and explains pagination via cursor. However, it does not explicitly state when to use this tool versus alternatives like get_billing_overview, leaving that differentiation to inference.

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