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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real context the annotations do not: this returns PHI, and the SSN is redacted — a meaningful behavioral disclosure for an agent handling patient data. It does not cover error behavior for a missing/invalid id, which keeps it from 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?

A single dense sentence pairing the field inventory with the PHI/SSN caveat, then the upstream endpoint. Front-loaded, zero filler, every clause earns its place.

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 carries the burden of telling an agent what returns, and it does so by enumerating the chart-header fields plus the SSN redaction. Complete enough to call correctly; only absence of missing-id/error behavior keeps it from a 5.

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 the single patient_id param is documented in the schema with its origin (elationhealth_list_patients) and type. The description adds no syntax or constraint detail beyond the schema, so the baseline of 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?

Specific verb ('Get') + resource ('one patient chart header') + retrieval key ('by id'), and it enumerates exactly which fields come back. An agent can distinguish this from elationhealth_list_patients purely by the 'one ... by id' framing 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 'by id' framing and the param note pointing to elationhealth_list_patients imply the correct usage context, but the description never explicitly states when to use this versus the sibling list/other get tools. Usage is inferable, not spelled out.

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