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

The readOnlyHint annotation already establishes this is a safe read, so the description only needs to add beyond that. It usefully clarifies that the result is document *references*, not document contents, and cites the underlying endpoint, but says nothing about pagination, result limits, or auth/scope requirements.

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?

One sentence with the core action front-loaded, followed by a compact endpoint reference. The parenthetical filter list is genuinely informative rather than filler; little 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?

For a read-only listing tool with no output schema, the description is nearly complete: it identifies the required patient scope, the optional filters, and the fact that references rather than contents are returned. Only pagination/response-shape 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%, so all four parameters (including the date patterns and the 3-char minimum for content) are already documented structurally. The description only restates the date-range and content-search filter categories, adding no syntax or default information 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 (List) and resource (document references for a Patient), plus the scope of optional filters. It is distinguishable from the document-query siblings (start_document_query, get_document_query_status, get_document_url) by resource, though it does not name any alternative explicitly.

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?

The phrase 'currently available for a Patient' and the optional date/content filters imply when to use it, but there is no explicit guidance on when to prefer this over get_document_url (to retrieve the actual file) or the query-status siblings. Usage context is implied rather than stated.

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