Launch Salesbot

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

Annotations include openWorldHint: true, which indicates external world interaction, but the description adds no behavioral details such as side effects, reversibility, or authorization requirements. Launching a salesbot likely has significant side effects, yet the description remains silent on them.

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, focused sentence with no redundancy. It is concise and front-loaded with the primary action. However, it could be slightly more structured by separating payload guidance from the overall purpose, but it remains appropriately brief.

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 action-oriented nature of this tool, no output schema, and only openWorldHint annotation, the description is insufficient. It omits return values, error handling, whether launch is synchronous, and any required permissions or conditions. The minimal description leaves many important context 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 only describes 'body' as 'Launch payload(s)', which is vague. The tool description adds meaningful context by specifying that the body 'typically includes bot_id and entity_id / entity_type', providing actionable guidance beyond the schema. This helps agents construct valid requests.

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 (Launch a Salesbot) and the target resource (entities), which distinguishes it from sibling tools like kommo_salesbots_list and kommo_salesbots_stop. However, it lacks detail on what 'entities' means specifically (e.g., leads, contacts, companies), which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The 'typically includes' phrase gives payload hints but does not explain the context or decision-making process for selection.

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