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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the 'Read-only' sentence largely duplicates structured data. The description does add genuine behavior beyond the annotations: the deterministic sort order (folders first, then name-sorted), which an agent needs to interpret result ordering.

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 short sentences, front-loaded with the scope and ordering, then the root/folder branching, then the hand-off to the download sibling. Every sentence carries information; no filler.

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?

No output schema exists, so the description partially compensates by noting a returned file id feeds drive_download_file. Pagination defaults and max are left entirely to the schema, which is acceptable, but the return shape (what fields a file entry has) is never sketched.

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 parentId, limit, and offset are already documented in the schema. The description's parentId explanation ('omit for root, pass folder id to list inside') restates the schema almost verbatim and adds no new syntax or format detail; baseline 3 is correct.

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 (files and folders in the account's Faivelo Drive) plus the ordering rule (folders first, then name-sorted). It is clearly distinguishable from sibling list_folders (mail folders) and list_messages by naming the Drive scope.

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 explicit conditional usage: 'Omit parentId to list the root; pass a folder's id to list inside it,' and routes the agent forward by naming drive_download_file as the follow-up for a returned file id. Nothing is left to inference.

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