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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the underlying REST mapping (GET /medical/v1/patient), which is useful context, but says nothing about pagination, result caps, or ordering — notable gaps for a list endpoint with no output schema.

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?

One tight sentence front-loads the behavioral rule (default = all, filter = facility) with the API path appended as supporting detail. 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 single-optional-param read tool with no output schema and annotations covering safety, the description covers the essential decision (filter or not). The only real omission is any hint about result size/pagination behavior, which a listing tool's consumer would benefit from.

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 parameter is fully documented there ('Optional Facility ID to filter by. Omit to list all patients.'). The description restates the same filter behavior without adding format, type, or edge-case 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?

The description gives a specific verb ('List') plus resource ('Patients') and nails down the scope: all patients, or only those at one Facility when facilityId is supplied. That scope distinction implicitly separates it from the singular sibling metriport_get_patient, though no sibling is named explicitly.

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?

It states the condition that widens or narrows the result ('only those at a given Facility if facilityId is supplied'), which implies the filter contract. There is no explicit when-to-use/when-not guidance and no reference to alternative tools such as metriport_get_patient or metriport_create_patient.

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