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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior, so the safety profile is covered. The description adds genuine context beyond that: it flags the response as PHI (sensitive data handling) and discloses the underlying Elation GET endpoint, which helps an agent reason about freshness and scope.

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?

A single compact sentence with the return payload front-loaded and the endpoint as a trailing technical note. No filler, no redundancy, and the most decision-relevant information comes first.

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 usefully enumerates the returned fields and marks the data as PHI, and annotations plus the schema cover safety and paging. A brief note on paging semantics or expected volumes would make it fully self-contained, but nothing essential for a correct call is missing.

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% – limit, cursor, offset, and patient are all documented in the schema, including default and max values and the source of the patient id. The description adds no parameter-level detail beyond the displayed 'GET /allergies/?patient=' endpoint, so the baseline 3 is appropriate.

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 one patient's allergies') and enumerates what is returned (allergen name, reaction, severity, status, start date). The resource is clearly distinct from siblings like list_medications, list_problems, and list_vitals, so an agent can disambiguate without opening a schema.

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 single-patient scoping ('one patient's allergies') implies when the tool applies, and the endpoint string hints at the required patient filter. However, there is no explicit when-to-use vs. alternatives guidance, no note about related siblings, and no prerequisites stated in prose (the patient-id provenance lives only in the schema).

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