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

readOnlyHint=true already establishes the safety profile, so the description's job is lighter. It still adds real value beyond the annotations: it discloses the paginated return shape ('page of patients plus next/previous URLs') and the underlying endpoint (GET /patients), which the annotations do not cover.

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, zero waste, front-loaded with what the tool does before the return shape and endpoint. The endpoint reference is compact and earns its place by grounding the tool in the DrChrono API.

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?

With no output schema, the description compensates by describing the return shape and pagination links, and it covers the filter surface. It is nearly complete, though it omits default page size behavior and sorting, which schema notes only partially cover.

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 all eight parameters are already documented with formats (ISO timestamp for since, yyyy-mm-dd pattern for date_of_birth, max 250 for page_size). The description only restates the filter categories and adds no format or semantics beyond the schema, 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?

States a specific verb+resource ('List/search patients in the practice') and enumerates the filterable dimensions, so the agent knows exactly what the tool retrieves. It differentiates from the sibling get_patient only implicitly through 'list/search', and never names an alternative, so it falls short of a 5.

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 word 'search' implies broad, filtered retrieval, which is adequate context, but there is no explicit when-to-use guidance, no statement about when to prefer drchrono_get_patient for a single record, and no prerequisites. Usage 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.