Add call notes

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

Annotations include only openWorldHint, with no readOnlyHint or destructiveHint, so the description must carry the behavioral burden. It states 'Add call notes' which implies mutation, but gives no details on side effects, permissions, return values, or consequences. The openWorldHint is not clarified.

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 two concise sentences with no filler. It front-loads the action and provides a useful field list. Every sentence earns its place.

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?

With no output schema, no parameter descriptions, and minimal annotations, the description should provide more context. It fails to explain what 'entities' means, how to structure the calls array, or what happens after adding. The tool is simple, but the lack of guidance leaves too many gaps.

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 input schema is minimal with a single 'calls' array and no property descriptions. The description compensates somewhat by listing typical fields: 'phone, source, duration, call_status, call_result, link, direction, uniq, created_at.' However, it uses 'typically' without explaining types or requirements, so the added meaning is incomplete.

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 a specific action: 'Add call notes (call in/out) to entities.' This clearly identifies the verb and resource, and the mention of 'call in/out' adds specificity. However, it does not explicitly differentiate from sibling tools like kommo_incoming_leads_add_call, which also adds calls but to incoming leads specifically.

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. It does not mention suitable entity types, prerequisites, or exclusions. There are many sibling tools for adding notes/calls, but no comparison or context is given.

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