Add users

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

With only an openWorldHint annotation and no readOnly/destructive hints, the description must disclose behavioral context. It does not mention permission requirements, idempotency, what happens to existing users, or validation behavior. 'Add users to the account' adds negligible insight beyond the tool name.

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 only one short sentence, but it is under-specified and merely restates the title and tool name. It lacks the substance expected for a create operation and does not earn its place by adding value.

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 that this is a create tool with an unstructured parameter array and no output schema, the description is severely inadequate. It fails to explain what constitutes a valid user object, what the response will be, or what permissions are needed. The annotation does not compensate.

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 0% description coverage; the 'users' array's object structure is completely unconstrained. The description does not explain what fields each user object must contain, the expected format, or any constraints. This leaves the agent without critical information for invocation.

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 'Add' and resource 'users' with scope 'to the account', clearly distinguishing it from sibling user tools like kommo_users_list, kommo_users_get, kommo_users_activate, and kommo_users_deactivate. It is unambiguous about the create semantic.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, exclusions, or context. It merely states the action without any situational or alternative-tool information.

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