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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuine value beyond that by disclosing the return shape ('a FHIR searchset Bundle'), which implies paged results. It does not mention pagination limits, _count behavior, or missing-patient handling, so it is solid 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?

Four short, front-loaded sentences: purpose, endpoint, filters, return type. No filler, no repetition, and the most decision-relevant information comes first.

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?

There is no output schema, so the description usefully characterizes the return as a FHIR searchset Bundle, and the schema covers filter syntax and _count. The only real gap is guidance on result limits/paging behavior and relationship to the broader search siblings.

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 five parameters are already documented in the schema, including prefix syntax for date and system|value for code. The description's filter list merely restates that coverage and adds no new syntax or constraint, 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 observations') and immediately disambiguates with concrete content examples ('labs, vitals') plus the underlying FHIR path. This lets an agent separate it from siblings like list_conditions, list_medications, or list_diagnostic_reports without opening anything.

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 names the available filters (category, LOINC code, date), which implies when the tool is the right choice, but never states alternatives or exclusions — e.g. when to prefer healthgorilla_fhir_search or healthgorilla_get_patient_everything over this targeted list. Usage is inferable but not guided.

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