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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add real value: it warns the payload may be large, that the return is XML/text passed through as-is unless JSON, and gives the exact endpoint. It does not cover permissions or any failure modes, but the format/size disclosure is meaningfully beyond the annotation.

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 and the format caveat immediately after. The trailing endpoint string is mildly redundant but does aid invocation, so nothing much is wasted.

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 usefully compensates by explaining the return format (XML/text, conditional JSON parsing) and size risk. The main remaining gap is the absence of any routing information relative to the sibling retrieval tools.

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?

With a single parameter at 100% schema coverage, the schema already documents particle_patient_id fully. The description reinforces the patient-scoped nature via the endpoint path but adds no syntax or format detail beyond the schema, so the 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 (the patient's C-CDA clinical document(s)), which is clearly narrower than mere FHIR or flat retrieval. It does not, however, explicitly contrast itself with siblings like particle_get_fhir, particle_get_flat, or particle_get_patient_documents, so the agent must infer the distinction from the format name 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 when-to-use guidance and no mention of alternatives. An agent cannot tell from this description when a C-CDA fetch is preferable to particle_get_fhir or particle_get_patient_documents, or what prerequisites (e.g., an existing query/patient record) might apply.

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