Delete role

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

The description adds no behavioral context beyond what annotations already provide. The word 'Destructive' merely repeats the destructiveHint=true annotation. It does not disclose any additional side effects, irreversibility details, permission requirements, or impact on related data.

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 extremely concise, consisting of two short sentences ('Delete a role by ID. Destructive.'). It is front-loaded and contains no filler, making it easy to parse quickly.

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 simple delete operation with a single parameter and annotations confirming destructive behavior, the description is minimally adequate. However, the openWorldHint suggests potential unstated side effects, and the description does not address what happens when deleting a role that is in use or if there are any return implications, leaving some 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?

With zero schema description coverage, the description's 'by ID' clarifies that the sole required 'id' parameter refers to the role's unique identifier. This adds meaning beyond the bare schema definition, though it does not elaborate on the integer type or range constraints.

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 with a specific verb and resource: 'Delete a role by ID.' This is unambiguous and distinguishes it from sibling tools like kommo_roles_get, kommo_roles_create, and kommo_roles_update.

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 usage (when you need to delete a role) but provides no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites or side-by-side comparison with related role operations.

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