insync_download_document

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

Adds real behavioral context beyond the annotations: the outcome differs by deployment (local install writes to disk and returns a path; hosted returns bytes inline), and the transfer is proxied through the portal rather than direct storage. Annotations already cover the read-only/non-destructive profile, so this is meaningful added value; it stops short of covering failure modes such as missing files or permission errors.

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?

Three tight sentences: what it does, how to identify the target, then the return behavior by deployment. Front-loaded and every sentence carries information.

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 takes on the burden of explaining returns and does so ('path returned' vs 'bytes come back inline'). Combined with the fully documented parameter schema and the read-only annotations, an agent has everything needed to call this correctly.

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%, and the schema already explains DstFolderURL, FileName, and the output_dir fallback/allowed-root rules. The description reinforces the provenance requirement but contributes no parameter detail the schema does not already contain, so 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 and resource ('Download a document filed to the patient's portal account') and scopes it to portal-filed documents rather than any file. An agent can immediately tell this is a document retrieval tool, distinct from list/get-style siblings.

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?

Gives a clear prerequisite chain — call insync_list_documents (full view) first and use its folder_url and file_name — which is exactly the context an agent needs before invoking. It does not, however, differentiate from the sibling insync_download_attachment or state when not to use this tool.

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