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

The readOnlyHint=true annotation already tells the agent this is a safe, non-mutating read, so the bar is lower. The description adds the underlying FHIR endpoint and the return type, modest useful context, but says nothing about auth requirements, error behavior for unknown ids, or cost. Adequate but not rich.

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?

Three short, front-loaded sentences with zero waste: action, endpoint, and return shape. Nothing repetitive or padded.

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 one-parameter read tool, the description covers the operation, the FHIR route, and the return shape, which compensates for the absent output schema. Only minor gaps (error handling, whether a Patient 360 enrichment exists) remain.

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 patient_id is fully documented in the schema. The description's 'by id' adds no meaning beyond 'Health Gorilla Patient resource id', so 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 (Read) and resource (a single patient by id), and the FHIR endpoint mapping (GET /Patient/{id}) reinforces exactly what is fetched. The singular 'single patient' implicitly distinguishes it from find_patients/search siblings, though it doesn't name them 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?

Usage is implied by 'by id' – call this when you already have a patient id – but there is no explicit when-to-use guidance, no mention of alternatives like find_patients or get_patient_everything, and no prerequisites stated.

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