Incoming leads summary

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

The annotations already declare `readOnlyHint: true`, and the description's 'Get' verb is consistent with that. However, the description adds no extra behavioral context such as authentication requirements, rate limits, or how the summary counts are structured. It is consistent but not additive.

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 conveying the core purpose without unnecessary jargon or repetition. It is concise and well-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?

With no output schema and zero parameters, the description should clarify what 'summary counts' includes (e.g., grouped by status, source, or overall total). The ambiguity could cause an agent to misunderstand the return format. However, for a simple no-parameter summary tool, it provides enough to differentiate from list/get tools, so it is minimally adequate.

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 input schema is empty with no parameters. The baseline for zero parameters is 4, and the description does not need to compensate for missing parameter details. It correctly adds no irrelevant parameter information.

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 uses the verb 'Get' and specifies the resource 'summary counts for incoming leads,' which is a specific action on a specific resource. It distinguishes from sibling tools like `kommo_incoming_leads_list` (lists leads individually) and `kommo_leads_summary` (summarizes all leads, not just incoming).

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?

The description implies usage for retrieving summary counts of incoming leads but does not explicitly state when to use this tool versus alternatives like `kommo_incoming_leads_list` or `kommo_leads_summary`. No exclusions or alternative references are given, so guidance is only implied.

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