Attach files to entity

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

The description discloses only the basic action, not behavior like whether this appends or replaces existing attachments, side effects, or whether the entity/file must exist. The 'openWorldHint' annotation is vague and the description adds little insight.

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?

One short sentence, front-loaded with the action, no wasted words. Perfectly concise and structured.

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 description is adequate for a simple attach operation, but it omits contextual details like whether the file UUIDs must come from a prior upload session, whether attachments are additive, or any error conditions. The schema provides entity_type options, but the description doesn't help the agent understand the full workflow.

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 coverage is 0%, but the description only clarifies that files are referenced by UUID. It doesn't explain entity_type or entity_id semantics beyond their names, leaving the agent to rely entirely on 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 uses a specific verb ('Attach') and resource ('files...to an entity'), clearly distinguishing it from sibling tools like kommo_files_entity_detach. The 'by UUID' qualifier adds precision about how files are referenced.

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?

There is no guidance on when to use this tool vs. alternatives. It doesn't mention prerequisites (e.g., file must exist, entity must exist) or contrast with detach/entities_with_file.

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