delete-drive-file

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

The annotations already declare the operation as destructive and non-read-only. The description adds meaningful behavioral context by emphasizing that deletion is permanent and that the file must already be in the trash, although it does not discuss permissions, error cases, or rate limits.

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 short, front-loaded with the permanent-delete scope, and then immediately gives the critical prerequisite. The required-parameters list and compact example are easy to scan without wasted prose.

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?

For a destructive two-parameter tool with full schema coverage and annotations covering safety traits, the description supplies the essential prerequisite and alternative action. No output schema exists, but the return behavior is not necessary for correct invocation here.

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 both parameters are already documented in the schema. The description repeats the required parameters and gives an example, but adds little semantic detail beyond the schema, which already notes that fileId must be in trash.

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 specific verb and resource: permanently delete a file from a Dooray drive trash. It distinguishes this operation from moving a file to trash by explicitly naming move-drive-file as the prerequisite alternative.

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?

It states the key precondition that the file must already be in the trash folder, and it names the exact alternative tool and parameter needed to get the file there first. This gives an agent explicit when-to-use and how-to-prepare guidance.

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