List incoming leads

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

The annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the scope 'unsorted/incoming leads in the inbox,' which is useful context. However, it does not disclose pagination behavior, return format, or how filtering interacts with the 'inbox' scope.

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, front-loaded sentence with no wasted words. It immediately states the action and target resource.

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 optional parameters, no output schema, and several sibling list tools, the description is too minimal. It does not explain how filters work, what 'incoming' means in relation to pipeline stages, or how this list differs from kommo_leads_list. The description leaves the agent without enough context to make informed decisions about parameter use.

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 only 17% (only filter_category has a description). The description does not compensate by explaining page, limit, filter_uid, order_created_at, or filter_pipeline_id. Parameter names are self-explanatory to some degree, but the description adds no additional meaning beyond the schema.

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 uses a specific verb and resource: 'List unsorted/incoming leads in the inbox.' This clearly identifies the tool's function and distinguishes it from siblings like kommo_leads_list (general leads) and kommo_incoming_leads_get (retrieve a single incoming lead).

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 about when to use this tool versus alternatives. Sibling tools like kommo_leads_list and kommo_incoming_leads_summary exist, but the description does not mention them or explain when this list is preferable.

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