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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a PHI sensitivity marker and the raw Elation endpoint, which is modest extra value but says nothing about pagination behavior or response size beyond what the schema's limit/cursor/offset fields already convey.

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: purpose and scope first, underscores the PHI nature and the concrete note types in the same breath. No filler, no restatement of the title, and the endpoint reference is compressed into one short clause.

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, single-filter list tool with all four parameters documented and safety annotations present, the definition covers what an agent needs to select and call it. The only gaps are what a note record contains (no output schema exists) and explicit paging guidance in prose, both minor since the schema carries the paging contract.

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% and every parameter (limit, cursor, offset, patient) is documented in the schema itself, including paging semantics and the provenance of the patient id. The description only echoes the patient filter via the endpoint string, adding no syntax or format detail 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 and resource ('List one patient's non-visit notes') and immediately scopes it as 'free-text chart notes outside a visit,' which cleanly separates it from the sibling elationhealth_list_visit_notes and elationhealth_get_visit_note. The concrete examples (phone calls, administrative notes) make the resource unambiguous without opening the 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 'outside a visit' qualifier gives clear context for when this tool applies versus its visit-note siblings, and it is patient-scoped. It stops short of an explicit exclusion sentence such as 'for notes attached to an encounter, use list_visit_notes instead,' so the routing 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.