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

The annotations include readOnlyHint=true, confirming this is a safe read operation. The description adds valuable context beyond the annotation: it requires authentication, and it returns upload status and accepted file formats. This discloses behavioral traits (auth need, return contents) without contradicting the read-only hint.

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 two sentences. The first sentence states the core purpose and target, and the second adds return content specifics and the authentication requirement. No filler or repetition; every sentence is purposeful and front-loaded.

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 that an output schema exists (as indicated in context signals), the description does not need to explain return values. It covers the tool's purpose, authentication, and key output elements (documents, upload status, formats). For a read-only tool with well-documented parameters, this is fully complete.

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 has 100% description coverage, with both order_id and bearer_token described. The description does not add extra parameter-specific semantics beyond mentioning the patient context. With the schema already handling parameter meaning, a 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?

The description clearly states the verb 'Get' and the resource 'documents a patient needs to upload for their order', distinguishing it from sibling tools like 'order_upload'. It also specifies that it returns required documents, upload status, and accepted file formats, making the purpose unmistakable.

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 gives clear context: use this tool to retrieve required documents for a specific order. It does not explicitly name alternatives or exclusions, but the phrase 'needs to upload' implies this is a prerequisite step before uploading. No explicit 'when-not-to-use' is provided, but the context is clear enough for a 4.

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