Update leads

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

Annotations (idempotentHint, destructiveHint) already cover safety and idempotency. The description adds the id requirement but does not clarify update semantics (e.g., partial vs full replace) or failure behavior. No contradiction with annotations.

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 two short sentences, front-loaded with the core action, and every word adds meaning. No filler or redundancy.

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 a single parameter, a detailed schema, and annotations, the description adequately covers usage. It could mention return behavior but is sufficiently complete for a batch update tool with low complexity.

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 coverage is high (100%) with detailed field descriptions. The description adds essential semantic value by requiring each object to include id, which is not enforced in the schema's item structure, and clarifies usage for a single lead.

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 the tool updates one or more leads, with a specific verb and resource. It distinguishes from related tools like kommo_leads_create and kommo_leads_update_one by noting batch capability ('one or more leads').

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 provides the prerequisite that each object must include id, and notes single-lead usage with id + fields. However, it does not explicitly mention alternatives like kommo_leads_update_one for single updates, leaving the choice of tool implied rather than stated.

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