Detach files from entity

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

The description adds a small amount of behavioral context beyond the annotations: the verb 'detach' implies the files are unlinked from the entity rather than permanently deleted, which is more specific than the generic destructiveHint. However, it does not disclose consequences such as whether the files remain accessible or how the operation affects file ownership.

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 sentence with no redundant words, meeting the conciseness criterion. The action is front-loaded and every word earns its place, though the brevity sacrifices useful detail.

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's three required parameters and lack of output schema, the description is too sparse to be complete. It does not explain the entity types supported, the format of the files list, or the outcome of the detach operation, leaving the agent under-informed for invocation.

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?

With schema_description_coverage at 0%, the description carries the full burden of parameter explanation, but it offers none. The agent must rely solely on parameter names like 'entity_type' and 'files' without any guidance on required values, the structure of the 'files' array, or the meaning of 'file_uuid'.

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 states the tool's action precisely: 'Detach files from an entity'—a specific verb and resource that contrasts with sibling tools like kommo_files_entity_attach. The one-sentence description is unambiguous and distinguishes its role among the sibling tools.

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 usage guidance is provided. The description does not mention when this should be used (e.g., to undo an attachment) or how it relates to kommo_files_entity_attach or listing endpoints, leaving the agent to infer context from the tool name.

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