Stop Salesbot

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

The only annotation is openWorldHint, which does not disclose behavior. The description does not explain side effects (e.g., whether it's reversible), required permissions, or impact on ongoing bot activities. With no meaningful annotation support, the description carries the full burden and falls short.

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, front-loaded with the key action and resource. It is appropriately short for a simple operation, though the extreme brevity omits useful context. No wasted words, but it could be slightly more informative without losing conciseness.

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 a nested body parameter, no output schema, and minimal annotations, the description leaves many unknowns: valid entity types, idempotency, potential errors, and what exactly happens when a bot is stopped. It is not complete enough for an agent to reliably invoke this tool without additional knowledge.

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?

Schema coverage is 50% (bot_id has no description, body does). The description adds that bot_id identifies the Salesbot, but the body parameter remains vague. It mentions 'for an entity' which loosely relates to the body, but doesn't clarify valid entity types or required fields within body. Partial compensation, but not enough to fully understand parameter usage.

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 (Stop) on a specific resource (Salesbot) and provides the scope ('for an entity by bot ID'). This is a specific verb+resource combination that distinguishes it from sibling tools like kommo_salesbots_launch.

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 given on when to use this tool versus alternatives like launch or list. There are no prerequisites, scenarios, or exclusions mentioned. The description only states the basic action without any contextual usage direction.

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