List roles

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds no additional behavioral context such as pagination behavior, return format, or permissions. The description 'List user roles' merely restates the title without enriching understanding.

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, which is appropriately brief for a simple list tool. However, it sacrifices useful detail, making it slightly under-specified. It earns points for brevity and front-loading the core purpose.

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 is a list operation with optional pagination and a mysterious 'with' parameter, yet the description provides no clarity on these. No output schema exists, so the description should explain what the agent can expect from the response, but it does not.

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 any of the three parameters (page, with, limit). While 'page' and 'limit' suggest pagination, 'with' remains ambiguous, and this ambiguity is not addressed. The description must compensate for the schema gap but fails to do so.

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 'List user roles' uses a specific verb (list) and resource (user roles), clearly distinguishing it from sibling kommo_roles_get which retrieves a single role. It unambiguously states the tool's function.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention that kommo_roles_get should be used for a specific role, nor any context about prerequisites or pagination. The agent gets no usage direction.

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