Deactivate users

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

Annotations already provide destructiveHint and openWorldHint, so the destructive nature is known. The description adds the 'bulk' detail, but does not disclose other behavioral traits such as reversibility, effects on user sessions, or whether deactivation is permanent.

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 with no filler. Every word contributes to the core meaning, 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?

The tool has low complexity (one parameter, no output schema) and annotations cover safety. However, the description lacks details about what deactivation entails, whether it is reversible, or any prerequisites, which is a notable gap for a destructive operation.

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 description coverage is 0%, and the description does not explain the 'users' parameter beyond implying an array. It does not state that each item requires an 'id' or what that id represents, leaving the schema to carry the full burden.

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 'Deactivate users in bulk' clearly states the action (deactivate), resource (users), and scope (bulk). It distinguishes itself from sibling tools like kommo_users_activate by specifying bulk deactivation.

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 for bulk deactivation but provides no explicit guidance on when to use this tool versus alternatives (e.g., kommo_users_activate) or any exclusions. Usage is inferred from the name and simple statement.

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