Organize files in Proton Drive

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

Annotations already indicate the tool is mutative (readOnlyHint=false) and may have side effects (openWorldHint=true). The description adds the dry-run behavior, but does not disclose details like what folder structure is created or if files are overwritten. 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?

The description is a single, clear sentence with no wasted words. It front-loads the action and purpose, making it efficient for an AI agent to parse.

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 complexity—organizing files with potential folder creation—the description lacks details about the structural logic, type classification, and conflict handling. No output schema exists, so descriptions should cover return behavior, but it does not. This leaves significant gaps.

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 50%; dry_run has a description that matches the schema, while staging_dir is undocumented. The description adds context by naming it 'staging directory', but does not fully compensate for the missing schema description. Baseline 3 applies as coverage is moderate.

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 'analyzes and moves' and the resource 'staging directory', with a specific action 'structured folder layout (by type)'. This distinguishes it from sibling tools like proton_drive_move, which moves individual files.

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 mentions 'Dry-run by default', which gives usage context, but does not explicitly state when to use this tool versus alternatives like proton_drive_move or proton_drive_list_files. The usage is implied but not fully delineated.

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