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

The description adds useful behavior beyond the annotations: pagination/filtering is mentioned, `data`/`id`/`ids` semantics are partially described, and bulk support is disclosed. However, it does not specify return format, auth needs, or side-effect behavior for the list action itself, leaving the behavioral picture incomplete.

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 text is short and begins with the resource and action, but it devotes space to get/create/update details that are irrelevant to a flattened list tool. The '[Flattened action: list]' line adds internal context rather than sharp user-facing guidance, so the structure is acceptable but not tightly focused.

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 10 parameters, no output schema, and sparse annotations, a list tool needs fuller details on list semantics, parameter syntax, return shape, and account scoping. The description covers only a small fraction of the required context and spends much of its length on non-list actions.

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 schema has 10 parameters with 0% description coverage, so the description must compensate. It explains `data` (body), `id`/`ids` (single vs bulk) to some degree, and hints at page/filter via 'busca paginada com filtros', but it does not define `with`, `limit`, `order`, `query`, `account`, or the expected formats for `filter` and `data`.

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 identifies the resource (Kommo leads) and the operation ('action: list ... busca paginada com filtros') and adds '[Flattened action: list]', so the core purpose is clear and distinguishable from the get/create/update siblings. However, it also enumerates get/create/update behaviors, blurring the focus and making the agent uncertain whether those actions are actually available in this flattened tool.

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?

It gives some usage context: list is paginated and supports filters, and bulk execution accepts ids. But it never explicitly says when to choose this list tool over kommo_leads_get or when not to use it, and no alternatives or exclusions are named.

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