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

The readOnlyHint annotation already establishes this is a safe read. The description adds useful context — that the result is a searchset Bundle that can be paged and synced incrementally — but is silent on auth requirements, record size limits, or how partial results are signaled. A modest addition over what annotations cover.

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 core purpose and progressive with capability then endpoint. The explicit endpoint string is mildly redundant given the tool name but is genuinely useful for an agent reasoning about the API surface.

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 carries the return-shape burden and does name the payload type (FHIR searchset Bundle) plus its incremental/paged nature. It stops short of describing what resource types appear in the bundle or how the next-page link is returned, but it is adequate for an agent to call the tool correctly.

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 coverage is 100%, so every parameter is already documented with type and meaning in the schema. The description corroborates the purpose of _since and _page_token through the 'incremental sync and pagination' phrase but adds no format or syntax detail beyond the schema. 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 (retrieve the patient's complete clinical record as a FHIR searchset Bundle) and scopes it as the full record, which implicitly separates it from filtered siblings like particle_get_fhir_by_type or particle_get_flat. It never names those siblings, so the differentiation is inferable rather than explicit.

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?

'Supports incremental sync and pagination' hints at when the _since and _page_token parameters matter, giving implied usage context. However, there is no statement of when to prefer this over particle_get_fhir_by_type or particle_get_ccda, and no exclusions or prerequisites are given.

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