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 meaningful context: the return format (FHIR searchset Bundle), support for incremental sync via _since, and pagination via _page_token. It does not mention rate limits or auth requirements, but adds solid value beyond annotations.

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 sentences, front-loaded with the core action and return type. The endpoint sentence is arguably unnecessary for an MCP tool but does not bloat the description. Every sentence carries some 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?

No output schema exists, so the description must explain the return value; it states the result is a FHIR searchset Bundle and covers pagination/incremental sync. It could elaborate on what clinical resources are included, but it is sufficiently complete for an agent to call the tool correctly given full schema coverage.

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 four parameters are already documented in the schema. The description only loosely ties 'incremental sync' and 'pagination' to _since and _page_token without adding syntax or format details beyond the schema. Baseline 3 is appropriate.

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 (Retrieve) and resource (patient's complete clinical record as a FHIR searchset Bundle). The scope 'complete clinical record' implicitly distinguishes it from particle_get_fhir_by_type, but does not name or explicitly contrast with the sibling.

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?

Mentions incremental sync and pagination, which are usage hints, but provides no guidance on when to choose this tool over alternatives like particle_get_fhir_by_type, particle_get_ccda, or particle_get_flat. No conditions or exclusions are given.

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