insync_list_documents

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description's real contribution is the behavioral hint that listing yields metadata only and contents require a separate download call, which is useful. It says nothing about ordering, pagination, or return shape, which are the remaining behavioral unknowns for a list endpoint.

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, purpose first, follow-up action second. No filler, no restating the tool name, every clause 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?

For a one-parameter read-only list tool with full schema coverage and complete annotations, the description covers the essential contract: what it returns at a high level and where the actual file contents live. The only shortfall is that an agent gets no sense of result ordering or whether the list is bounded, which matters for a document catalog.

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 single `view` enum is thoroughly documented in the schema itself, including what compact/full/raw each return. The description adds nothing about `view`, which is acceptable given the schema does the work, 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?

Names a specific verb and resource ("List documents filed to the patient's portal account"), scoping the resource to one patient's account, which cleanly separates it from siblings like insync_list_attachments or insync_list_forms. It stops short of naming the download sibling by exact name, but "the download tools" is close enough to disambiguate.

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 second sentence explicitly routes the agent to the download tools when it needs file contents, which is the key decision point against insync_download_document. It gives no guidance on when this tool would be the wrong choice beyond that (e.g., form or attachment catalogs), so a small exclusion gap remains.

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