kommo_link_product_to_lead

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

No annotations are provided, so the description carries full burden. It only says 'Link' implying a mutation, but does not disclose whether existing links are replaced or added, what quantity means, what happens on failure, or required permissions. The description is insufficient for behavioral transparency.

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 concise sentence of 8 words. It is front-loaded and wastes no words. However, it sacrifices completeness for brevity, missing key details that could be added without significant length.

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 has 3 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, side effects, error conditions, or preconditions. The description alone is inadequate for safe and effective tool use.

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 0% schema description coverage, the description should compensate, but it adds no meaning beyond parameter names. It does not explain what leadId or productId refer to, nor what quantity represents (e.g., units, sets). The description fails to help the agent understand parameter semantics.

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 the verb 'Link' and the resources 'product/catalog element' and 'lead'. It distinguishes from sibling tools like kommo_unlink_product_from_lead and kommo_link_lead_to_contact. However, it could be more precise by indicating that the product is from a catalog, but the purpose is clear enough.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., lead and product must exist), and no context about when linking is appropriate. This lack of usage direction makes it hard for an agent to decide correctly.

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