kommo_create_lead

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

No annotations provided, so description carries full burden. It mentions optional contact linking but does not disclose side effects (e.g., duplicate handling), required permissions, or response behavior. Inadequate for a mutation tool.

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?

Single sentence covering key functionality. Concise and front-loaded, but could be more informative about other parameters.

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 8 parameters, no output schema, and no annotations, the description is too brief. It omits explanation of return values, behavior for missing optional fields, and interaction with other entities.

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?

Only 13% schema description coverage. The description explains that contact_name and contact_phone are for linking a contact and custom_fields_values for custom fields, but five parameters (price, status_id, pipeline_id, responsible_user_id) remain unexplained. Insufficient compensation for low coverage.

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 states that the tool creates a lead, with optional contact linking and custom field setting. It distinguishes from siblings like kommo_create_contact (creates only contacts) and kommo_update_lead (updates existing).

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 on when to use this tool versus alternatives (e.g., kommo_create_contact for contacts only, or kommo_update_lead for modifying an existing lead). No prerequisites or context provided.

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