Link entities

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

With only openWorldHint annotation (which is a schema hint, not a safety/behavior hint), the description shoulders most of the burden. It discloses the metadata caveat for catalog links, but does not state that this is a mutating operation, mention side effects, or describe return behavior. This is adequate but not rich.

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?

Two sentences, no filler. Effectively front-loaded with the primary action and immediately provides the critical parameter details.

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 mutation operation with no output schema and minimal annotations, the description is somewhat thin. It explains what is needed but omits any mention of return values, error behavior, or the effect of creating a new link. Still, the core usage is clear and sufficient for an agent to attempt the call.

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 schema has 0% description coverage and the links item is an open object with no property definitions. The description compensates by naming the internal fields (to_entity_id, to_entity_type) and the metadata requirement, adding essential meaning beyond the raw 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 the action: 'Link entities to a parent.' It uses a specific verb and resource, and the mention of required fields (to_entity_id, to_entity_type) distinguishes this from sibling tools like kommo_links_list and kommo_links_unlink.

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 gives clear context on how to use the tool, specifying that each link needs to_entity_id and to_entity_type, and notes a special case for catalog links. It implies this is for creating new links but does not explicitly mention alternatives or when not to use it.

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