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

With readOnlyHint already providing safety information, the description adds valuable behavioral context by noting that authentication is required and that the response includes upload status and accepted file formats. This goes beyond the annotation without contradicting it.

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?

The description is compact and front-loaded, with two sentences that directly convey purpose, return content, and authentication. No unnecessary words or repetition.

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?

Given the tool's simplicity, presence of an output schema, and readOnly annotation, the description sufficiently covers purpose, key return elements, and auth. It provides enough context for an agent to invoke the tool correctly without needing further explanation.

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?

The input schema already provides full descriptions for both parameters (order_id and bearer_token), so the baseline is 3. The description does not add further parameter-specific details beyond what the schema already covers.

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?

Description clearly states the tool retrieves the list of documents a patient must upload for an order, using the specific verb 'Get' and the resource 'list of documents'. It distinguishes from siblings like order_upload by focusing on fetching requirements rather than performing the upload.

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 description establishes clear context: it is used to check required documents for a specific order, with no exclusions or alternatives mentioned. While it doesn't explicitly name sibling tools or state when not to use it, the context is unambiguous enough for selection.

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