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

Annotation readOnlyHint=true already establishes the safe-read profile, and the description adds genuinely new behavior: results are paginated with next/previous links, which matters because there is no output schema. It stops short of stating defaults or max page size (those live in the schema), so a 4 rather than a 5.

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 clauses covering purpose, filtering, and return shape, with the core action front-loaded. Every sentence earns its place and there is no filler.

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 read-only list tool with full schema coverage and an annotation carrying the safety profile, the description supplies the remaining gap (pagination/next-previous return shape). It is essentially complete, though it omits default page size and ordering, which an agent might want.

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 the schema already documents page, page_size, doctor, and patient with defaults and bounds. The description's "filterable by patient or doctor" restates the schema rather than adding format or constraint 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 allergies") and names the DrChrono endpoint, which makes it unmistakable against list siblings like list_medications or list_problems. It does not explicitly contrast itself with those siblings, so it falls just 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 description mentions that results are filterable by patient or doctor, which hints at usage, but gives no when-to-use/when-not guidance and never names an alternative tool for retrieving allergy data by another route. Nothing tells the agent when this list is the right call versus a more targeted fetch.

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