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

The readOnlyHint=true annotation already establishes this is a safe read, so the bar is lower. The description adds that the result is a whole-patient Bundle that can be date-scoped and paginated, which is useful context, but it omits any warning about payload size or cost typical of $everything operations.

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 sentences, front-loaded with the verb, resource, and return type, then the exact FHIR path, then the optional modifiers. Every sentence carries information with 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?

With no output schema, the description correctly tells the agent the return is a FHIR Bundle, and it covers optional scoping/paging. It leaves a minor gap in not flagging the potentially large volume of a $everything response, but nothing needed to invoke it correctly is missing.

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 patient_id, _since, and _count are already fully documented in the schema. The description merely names _since and _count without adding format or interaction details beyond what the schema provides, matching the baseline 3.

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 (fetch), resource (patient's comprehensive record), and return shape (FHIR Bundle), plus the exact FHIR operation GET /Patient/{id}/$everything. The word 'comprehensive' implicitly separates it from the single-resource get_patient and the granular list_* siblings.

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 description explains how to scope (_since) and page (_count) results, but never says when to choose this over siblings like healthgorilla_get_patient or the list_* tools. Usage is only implied by the word 'comprehensive' rather than stated with an exclusion or alternative.

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