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 only the raw endpoint path, which is technical trivia rather than behavioral context — nothing about pagination, result limits, ordering, or whether an empty list vs. error is returned when a patient has no documents.

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 short sentences with the purpose front-loaded and no filler. The endpoint sentence is arguably redundant but is the only concrete detail offered, so it is not wasted space.

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?

For a one-parameter read-only list tool with no output schema, the definition covers the minimum, but it omits return-shape and pagination expectations, which matter for a documents listing endpoint. Adequate but with a clear gap.

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% with a single required patient_id that is already documented as 'Patient id whose documents to list.' The description restates that scoping but adds no format, source-system, or identifier-type detail beyond the schema, 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?

States a specific verb+resource: 'List the documents uploaded / available for a patient.' An agent knows what it returns, but the description never distinguishes it from siblings like particle_get_ccda or particle_get_fhir, which also retrieve patient clinical data. The 'uploaded / available' hedge also blurs whether this covers both uploader metadata and document content.

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?

No when-to-use guidance, no exclusions, and no pointer to alternatives among the ten sibling tools. The description gives no condition under which this tool is the right choice versus particle_get_fhir or particle_get_ccda.

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