drive_list

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

Annotations already provide readOnlyHint and idempotentHint. The description adds behavioral context: requires authentication, returns a specific structure, clarifies non-recursive behavior. No contradictions with annotations.

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?

Every sentence earns its place. Front-loaded with the core action and resource. No redundancy or filler. Efficiently conveys purpose, usage, return format, and alternatives in under 50 words.

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 (1 param, no output schema), the description is complete. Explains return format, scope (non-recursive), gives concrete use cases, and directs to relevant siblings. No gaps for an agent to invoke 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 coverage is 100% for the single 'path' parameter. The description adds meaning: 'Absolute remote Drive path (must start with '/')' and provides examples like '/my-files' and '/my-files/Reports'. This goes beyond the schema's basic description.

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?

Clearly states 'List the immediate children of a Proton Drive folder' – a specific verb ('List') and resource ('immediate children of a folder'). Differentiates from siblings by noting it is not recursive and does not list trash.

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?

Explicitly provides when to use: 'Use before drive_upload to confirm the destination exists, or before drive_download to verify the remote path.' Also states when not to use: 'Do not use to list trash — use drive_list_trash instead.' Offers clear alternatives.

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