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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read nature is covered. The description adds useful details about the 'with' parameter and bulk ids support, but does not disclose more significant behavioral aspects such as output shape or pagination behavior.

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 short and mostly to the point, but the phrase 'action: list | get' combined with '[Flattened action: get]' creates redundancy and some noise. It is terse but not optimally structured.

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 there are 6 parameters and no output schema, the description provides only enough context for a basic understanding: users, get by id, with expansion, and bulk support. Missing details about page/limit, id vs ids usage, and return semantics keep it from being fully complete.

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?

There is zero schema description coverage, yet only the 'with' parameter is explained as accepting role/group, and 'ids' is only generally mentioned for bulk support. Core parameters such as id, page, limit, and account are not described or distinguished in the description.

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 identifies that the tool deals with users of the account and that it fetches users by id ('get (por id)') with optional bulk support. The mention of 'action: list | get' creates some ambiguity, especially given that a sibling tool kommo_users_list exists, but the core resource and verb are present.

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?

Usage is mostly implied: the description signals that 'with=role,group' includes permissions/groups and that bulk execution is supported via ids. However, it does not explicitly explain when to prefer this tool over kommo_users_list or state exclusions/alternatives.

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