Drive list

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds the RCLONE_REMOTE prerequisite, which is useful, but it does not disclose expected output format, pagination behavior, error handling, or any network/rate implications. Given the annotations cover the safety profile, the description adds minimal additional behavioral context.

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 concise sentence that front-loads the core action and resource. It is efficient and avoids fluff. The inclusion of the RCLONE_REMOTE prerequisite is valuable. It is slightly terse but structurally sound.

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 has two parameters with zero schema descriptions, an output schema exists but the description does not reference it, and annotations are sparse, the description is incomplete. It does not explain how to construct a path (e.g., remote:folder), what max_entries does, or how results are returned. A more complete description would provide examples or clarify parameter semantics.

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 0%, and the description provides no parameter documentation. The path parameter is implied by 'remote path' but not explained in terms of format or examples, and max_entries is entirely undocumented. The description fails to compensate for the missing schema descriptions, leaving agents guessing about valid inputs.

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 action 'List' and the resource 'rclone remote path', which is specific enough to distinguish from local file listing tools like list_directory. The prerequisite 'needs RCLONE_REMOTE' adds context. However, it does not specify whether the listing returns files, directories, or both, leaving some ambiguity about the exact 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?

No guidance is given on when to use this tool versus alternatives. The sibling list includes list_directory, file_search, and drive_get, but the description does not differentiate drive_list from these or explain when a remote listing is appropriate. The only hint is the RCLONE_REMOTE prerequisite, which is an environmental requirement rather than a usage condition.

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