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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: it discloses pagination semantics ("Returns a page plus `next`/`previous`") and identifies the underlying DrChrono endpoint, which helps an agent plan multi-page retrieval.

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 tight sentences: the core operation and filters come first, followed by return-shape and endpoint details. Every clause earns its place with no padding.

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 low-complexity read-only list tool with full schema coverage and a declared readOnlyHint, the description covers purpose, filters, and pagination/return shape. The absence of an output schema is mitigated by the "page plus next/previous" note, leaving little an agent would need that isn't present.

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 four parameters (page, doctor, patient, page_size) are already documented in the schema, including defaults and max values. The description's "filterable by patient or doctor" restates this without adding format or edge-case detail, 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 and resource ("List patient medications") and its filter dimensions, which cleanly separates it from siblings like drchrono_list_allergies, drchrono_list_problems, and drchrono_list_lab_orders. It does not explicitly name a sibling it differs from, but the resource is unambiguous.

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 phrase "filterable by patient or doctor" implies when the tool is useful (retrieving a specific patient's or doctor's medications), but there is no explicit when-to-use/when-not guidance or reference to an alternative tool. 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.