Restore files

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

The description provides no behavioral details beyond the action itself. It does not disclose side effects, whether restore is reversible, permission requirements, or error conditions, and the openWorldHint annotation does not mitigate this gap.

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, direct sentence without unnecessary words, making it very concise. However, it is under-specified, but that is more a completeness issue than a conciseness issue.

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?

As a mutation tool with no output schema and minimal annotations, the description is inadequate. It does not explain what happens after restore, how to obtain the UUIDs, or any special conditions, so the agent may not know how to invoke it correctly.

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 does not mention the 'files' parameter or provide any guidance on its structure or required UUIDs. With 0% schema description coverage, the description fails to compensate, leaving the agent to infer the parameter semantics solely from the schema.

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 a specific action (restore) and resource (previously deleted files), distinguishing it from sibling file tools like kommo_files_delete and kommo_files_list.

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 usage for files previously deleted, but does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites such as needing the file UUID from a deletion or listing operation.

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