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

Annotations already declare it as read-only and idempotent, so the safety profile is covered. The description adds useful context about bulk support (accepts ids) and the 'with' parameter for enriching results. However, it does not describe return format, pagination behavior, or any side effects beyond what annotations imply. It does not contradict annotations.

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 brief but somewhat cluttered with cryptic phrases like 'Flattened action: list' and 'action: list | get (por id)'. The structure is not ideal—multiple lines and a bracket notation that adds noise. It is concise but could be clearer and more organized.

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?

With 6 parameters, no output schema, and zero schema documentation, the description is insufficiently complete. It lacks explanations for pagination, filtering, the 'account' parameter, and expected return data. For a simple listing tool, a brief mention of output structure would be expected; this is missing.

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%, so the description must explain parameters. It only elaborates on 'with' (role/group) and hints at 'ids' for bulk. Parameters like 'id', 'ids', 'page', 'limit', and 'account' are left unexplained, leaving significant ambiguity for an agent.

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 states it deals with account users and supports list and get by id actions. The primary purpose is listing, as indicated by 'Flattened action: list'. However, it doesn't clearly differentiate from the sibling tool kommo_users_get, which exists specifically for getting a single user, causing slight ambiguity.

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?

There is no explicit guidance on when to use this tool versus alternatives. It mentions the 'with' parameter for including permissions/groups and bulk support, but does not explain when to prefer this over kommo_users_get or other list tools. No exclusions or alternative recommendations are provided.

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