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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful context beyond that: the underlying FHIR call and the return shape ('a FHIR searchset Bundle'), which tells the agent what to expect back. It omits pagination/rate-limit behavior, but for a read-only list this is solid.

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 primary action before the endpoint, filters, and return type. Every sentence carries information and nothing is 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?

With no output schema, the description correctly compensates by naming the return type (FHIR searchset Bundle) and the filter options. Pagination is only covered via the _count schema field, not the description, which is the only minor gap for a 5-parameter search tool.

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 the schema already documents each parameter with examples and FHIR semantics. The description restates the filter axes (category, LOINC code, date) but adds no syntax or format detail beyond what the schema provides, 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?

The description uses a specific verb+resource ('List a patient's observations'), scopes it to a patient, and names concrete examples (labs, vitals) plus the FHIR endpoint. This clearly distinguishes it from siblings like list_allergies, list_conditions, and list_diagnostic_reports.

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 lists the available filter dimensions (category, LOINC code, date), which implies when the tool is useful, but never states when to prefer it over alternatives such as healthgorilla_fhir_search or healthgorilla_get_patient_everything. No exclusions or prerequisite guidance are given.

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