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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context beyond that: the REST/FHIR mapping (GET /Immunization?patient={id}) and the return shape (a searchset Bundle). It stops short of describing pagination behavior or auth requirements, so it is useful 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 sentences with no waste: purpose first, then the FHIR mapping, then the return type. Every sentence carries information an agent can use.

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 usefully discloses that a FHIR searchset Bundle is returned, and the two-parameter surface is simple. It could say more about paging through large result sets, but for a read-only list tool it is nearly complete.

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 both patient_id and _count are already documented in the schema. The description only echoes the patient={id} binding and adds no semantics for _count or paging limits, 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?

States a specific verb and resource scoped to a patient ('List a patient's immunizations') and even names the underlying FHIR interaction, so it is unambiguous. It does not explicitly distinguish itself from siblings like healthgorilla_get_patient_everything, which may also carry immunization data, but the resource name makes the target obvious.

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?

There is no statement of when to use this tool versus alternatives such as healthgorilla_fhir_search or healthgorilla_get_patient_everything, and no prerequisites or exclusions are given. The only usage signal is the patient scoping implied by the name.

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