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 genuine behavioral context beyond that: the document may be 'large' and can come back as raw XML/text rather than structured JSON, which is useful for downstream handling. It stops short of saying how multiple documents are ordered/returned or whether retrieval is paginated.

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?

Two tight sentences with the purpose front-loaded, followed by the payload/format caveat and the endpoint. Nothing is padding, though the endpoint restates what the prose already implies about the resource.

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 describing what comes back (XML/text, JSON parsed) and warning about payload size. For a single-parameter read-only tool whose safety profile is covered by annotations, that is nearly sufficient; only multi-document/pagination behavior is unaddressed.

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% for the single particle_patient_id parameter, so the schema already carries the semantics and the baseline is 3. The description reinforces the id by embedding it in the endpoint path but adds no format or sourcing detail beyond the schema.

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 (C-CDA clinical document(s)) for a named patient, and the endpoint line reinforces the exact scope. However, it never distinguishes itself from the near-identical siblings particle_get_fhir, particle_get_flat, and particle_get_patient_documents, so an agent cannot tell which format-route to pick from the text alone.

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?

There is no explicit when-to-use guidance and no mention of any alternative tool. The format note ('parsed if JSON, otherwise passed through as-is') describes output shape, not when to choose this over particle_get_fhir or particle_get_flat, which retrieve the same patient's data in other formats.

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