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

Annotations declare readOnlyHint=true, so safety is already covered; the description goes further by naming the underlying FHIR endpoint and the response shape ('FHIR searchset Bundle'), which tells the agent to expect paged Bundle semantics. It stops short of stating auth requirements, hard result limits, or how paging links are followed.

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 filler; the purpose is front-loaded, followed by the endpoint and return type in priority order. Every sentence carries distinct information.

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 simple read-only list tool with full schema coverage and no output schema, the description covers purpose, endpoint, and return format adequately. The remaining gap is paging/category behavior, which the schema touches on only briefly.

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 three parameters are already documented. The description only restates the patient filter via the FHIR template ('patient={id}') and adds nothing about category value semantics or _count paging behavior, 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 ('List a patient's conditions/problems') and pins the exact FHIR operation being proxied, so the agent knows precisely what it does. It does not, however, distinguish itself from siblings such as healthgorilla_fhir_search or healthgorilla_get_patient_everything, which could also surface conditions.

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 strongly implied by the name and the required patient_id, but there is no explicit when-to-use statement and no guidance on when to prefer this over healthgorilla_fhir_search or get_patient_everything. The FHIR path adds context but not decision guidance.

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