twake_drive_list

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

There are no annotations, so the description must carry behavioral disclosure. It only states the action (list files/folders) without mentioning relevant behavior such as whether listing is recursive or limited to immediate children, required access permissions, or whether only metadata is returned. This is minimal for a read-only tool, but still leaves key traits undisclosed.

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 with no wasted words and the core action is front-loaded. It is appropriately sized for the tool's complexity.

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?

The tool is low-complexity with one optional parameter documented in the schema, and the description sufficiently conveys what operation is performed. It does not define return structure, but with no output schema and such a simple listing action, this is a minor gap rather than a blocker.

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 path parameter already has a clear description ('Folder path or ID (default: /)'). The tool description adds no additional parameter meaning, but the schema fully covers the optional path, so the baseline of 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?

The description uses a clear verb ('List') and specifies the resource ('files and folders in Twake Drive'), so an agent can understand the operation. It does not explicitly differentiate itself from sibling tools like twake_drive_read or twake_drive_upload, but the listing intent is unambiguous.

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 implies this is the tool to call when you need an inventory of drive contents, and sibling names suggest alternatives for reading or uploading. However, no explicit when-to-use, when-not-to-use, or alternative conditions are stated.

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