kommo_get_leads_by_contact

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

Annotations are absent, so the description carries full burden for behavioral disclosure. It only states 'Get all leads associated with a contact' without revealing traits like pagination, authentication needs, rate limits, or whether the operation is read-only. The description provides no behavioral insights beyond the basic purpose.

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, clear sentence with no extraneous words. It is front-loaded with the key action and resource. Every word earns its place.

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?

Given the low complexity (1 param, no output schema, no annotations), the description is minimally complete. It states the core purpose but omits details like the structure of the returned leads, whether links are direct or transitive, and any edge cases. A slightly richer description would improve completeness without adding clutter.

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 the 'contactId' parameter beyond its name. While the parameter's role is inferable from context, the description adds no meaning to the schema definition. For a single parameter, even brief clarification (e.g., 'the ID of the contact to retrieve leads for') would improve this score.

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 'Get all leads associated with a contact' uses a specific verb ('Get') and resource ('leads'), clearly indicating a filtered retrieval operation. It distinguishes itself from sibling tools like 'kommo_get_lead' (single lead) and 'kommo_list_leads' (unfiltered list) by specifying the association with a contact.

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. For example, it does not compare against 'kommo_list_leads' or 'kommo_search_lead' for filtering by contact. The description implies usage context but offers no explicit when-to-use or when-not-to-use information.

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