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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description goes beyond that by disclosing the pagination return shape ('a page plus `next`/`previous`'), which is meaningful since there is no output schema, and by mapping to the underlying DrChrono endpoint. It does not mention auth requirements or rate limits, but the annotation bar is already met.

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, front-loaded with the core purpose and filter scope, then the return shape, then the API mapping. No filler or redundancy; each sentence carries distinct information.

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?

All five optional parameters are documented in the schema, and the description compensates for the absence of an output schema by describing the paginated return with next/previous. It is complete for a read-only list tool, though it could note ordering or default page_size behavior for full coverage.

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 description coverage is 100%, so every parameter is already documented in the schema. The description restates the same filters (doctor, patient, since) without adding format, syntax, or interaction details beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource ('List patient payments (billing)') and immediately scopes it with the available filter dimensions. An agent can distinguish this from siblings like drchrono_list_line_items or drchrono_list_patients without opening the schema, especially with the '(billing)' qualifier.

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 names the filter options (doctor, patient, last-modified time), which implies when the tool is useful, but it offers no explicit when/when-not guidance or named alternatives among the many list_* siblings. Usage is implied rather than stated.

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