List Salesbots

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

The readOnlyHint and openWorldHint annotations already establish the read-only, side-effect-free nature, and the description aligns with them. However, the description adds no extra behavioral context, such as pagination, sorting, or the effect of the 'favorite' parameter on the response.

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 that immediately states the tool's function. No filler or redundant words are present, making it optimally front-loaded.

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 simple list operation with one optional parameter and read-only annotations, the description is mostly complete. It lacks explicit mention of return format or pagination, but these are not critical for such a straightforward tool given the schema coverage.

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 has 100% description coverage for the single 'favorite' boolean parameter. The tool description itself does not mention parameters, but the schema fully describes the only parameter, so the description need not add more.

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 'List Salesbots in the account' uses a specific verb and resource, clearly identifying it as a list operation. It naturally distinguishes from sibling tools like kommo_salesbots_get (single retrieval), launch, and stop by describing the list action.

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 about when to use this tool versus alternatives, nor any mention of when not to use it. There is no explicit context or exclusion suggested, leaving the agent to infer usage solely from the name.

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