Get Salesbot

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

The description adds no behavioral context beyond the annotations. The readOnlyHint and openWorldHint already indicate this is a safe, read-only operation, but the description does not disclose other relevant behaviors such as response format, error handling, or what happens if the ID does not exist.

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, front-loaded sentence with no filler. It immediately states the action and target, fully earning 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?

For a simple get-by-ID operation with read-only annotations, this description is minimally adequate for selecting the tool and understanding its basic purpose. However, it lacks detail about the return value (especially since there is no output schema) and provides no context about the Salesbot resource itself.

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 required integer 'id' with no description (0% coverage). The description's 'by ID' essentially restates the parameter name and tool purpose, adding no additional meaning about the ID's format, domain, or constraints beyond the schema's type and range.

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 ('Get') and resource ('Salesbot') with clear scoping ('by ID'). This distinguishes it from sibling tools like kommo_salesbots_list (which lists salesbots) and kommo_salesbots_launch/stop (which act on salesbots).

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 offers no explicit guidance on when to use this tool versus alternatives. It does not mention kommo_salesbots_list for retrieving multiple salesbots or any selection criteria. The phrase 'by ID' implies a known identifier, but no alternatives or exclusions are stated.

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