kommo_list_leads

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

No annotations are present, so the description must fully convey behavior. It only mentions 'with filters' but does not disclose pagination (page, limit parameters exist), data ordering, rate limits, or the nature of the mutation (read-only). The description is insufficient to understand the tool's behavioral traits.

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?

At only four words, the description is under-specified rather than concise. It lacks key information that would justify its brevity, such as linking to external documentation or providing essential usage details.

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 5 parameters, no output schema, and no annotations, the description provides almost no context. It does not clarify the filtering logic (AND/OR), default limit, result format, or any prerequisites. This is completely inadequate for an agent to use effectively.

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 description adds little meaning beyond the schema parameter names. It says 'with filters' but does not explain how to use the specific parameters (status_id, pipeline_id, etc.) or their allowed values. With 0% schema description coverage, the description should compensate 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 states 'List leads with filters,' which is a verb+resource combination. However, it does not distinguish this tool from siblings like kommo_search_lead or other list tools that also operate on leads. The description is minimal and lacks specificity about the type of leads or filtering capabilities.

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 such as kommo_search_lead or kommo_list_deals. There are no explicit when-to-use, when-not-to-use, or alternative recommendations.

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