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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful behavior beyond that: name matching is exact and case-insensitive with no partial names, and SSN is redacted, which an agent needs to know before querying.

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?

Front-loads purpose, then matching semantics, then the PHI redaction note, with a trailing API endpoint reference. Every sentence carries information; only the raw endpoint reference is marginal.

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 zero required parameters, full schema coverage, and annotations covering the safety profile, the description supplies the extra context (matching rules, redaction) needed to query correctly. Pagination mechanics live in the schema, so their absence from the description is acceptable.

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 nine parameters are already documented in the schema. The description's note about exact, case-insensitive name matching largely restates the schema's own wording for first_name/last_name, so it adds little beyond the baseline.

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 (Search) and resource (patient charts/PHI) and enumerates the returned fields, which clearly frames this as a patient lookup/list operation. It does not explicitly differentiate from the sibling elationhealth_get_patient, though the plural/search framing makes the distinction inferable.

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?

Usage is implied (search the practice's patient charts) but there is no explicit when-to-use guidance or reference to alternatives such as elationhealth_get_patient for single-record retrieval. No exclusions or prerequisites are stated.

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