Delete files

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

The description only repeats 'Destructive,' which is already declared by destructiveHint=true in annotations. It adds no new behavioral context such as whether deletion is permanent, supports batch deletion, or affects linked entities. No annotation contradiction exists.

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 extremely concise, consisting of two short sentences. It front-loads the action and includes a concise destructive warning, with no unnecessary 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?

For a simple delete operation, it is minimally adequate, but lacks critical context such as return values, irreversibility, permission requirements, and batch behavior. The absence of an output schema makes the lack of return-value information more impactful.

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?

The description merely states 'by UUID,' which adds minimal meaning beyond the schema's 'files' array of objects with 'uuid.' With 0% schema description coverage, the description fails to explain that multiple files can be deleted or how the array should be structured.

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 'Delete files by UUID' uses a clear verb+resource and specifies the identifier type. It clearly distinguishes from sibling tools like kommo_files_restore and kommo_files_edit, and the additional word 'Destructive' reinforces the action.

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 provided on when to use this tool instead of alternatives such as restore or edit. There are no prerequisites, reversibility notes, or context about permanent vs. soft deletion, leaving the agent to infer usage.

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