Add call notifications

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

The description adds some context (running call, caller ID/softphone UX) but does not disclose any side effects, permissions, or what happens after notification. The openWorldHint annotation already signals open-ended behavior, but the description does not enrich it with specifics like whether the call record is created or if there are ordering constraints.

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, tightly worded sentence that front-loads the action and context. No unnecessary words or filler; it earns its place by conveying the core purpose efficiently.

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 tool with an open schema and no output schema, the description is insufficient for an agent to successfully invoke it. It lacks any explanation of the input format, expected behavior, or return value, and does not fully clarify the difference from similar call-related tools.

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 one parameter 'notifications' but provides no property definitions (additionalProperties: {}), and schema description coverage is 0%. The description does not mention the parameter at all, leaving the agent with no guidance on how to structure the array or what fields to include.

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 ('Notify') and identifies the resource ('Kommo about a running call for a phone number'). It clearly distinguishes from sibling tools like kommo_calls_add by emphasizing the real-time 'running call' aspect and caller ID/softphone UX context.

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 implies when to use the tool (during a running call, for caller ID/softphone UX) but does not explicitly mention alternatives or when not to use it. No exclusions are stated, and there is no reference to sibling tools for comparison.

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