kommo_update_lead_custom_fields

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

With no annotations provided, the description carries full burden for behavioral traits. It does not disclose whether fields are merged or replaced, idempotency, permission requirements, or error conditions. This leaves critical behavioral gaps.

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?

Extremely short (6 words) but lacks necessary details for a mutation tool with two parameters. Conciseness is not beneficial here because it omits essential information.

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?

The description is incomplete: no output schema, no behavior details, no usage notes. For a tool that modifies custom fields, the description should mention whether existing fields are overwritten, how to retrieve current fields, and any restrictions.

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 schema has 50% description coverage (only 'fields' has a minimal description). The description 'by name' adds some context but does not compensate for the missing leadId description. No details on value format or constraints.

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 identifies the tool updates custom fields of a lead, specified by name, distinguishing it from general lead updates like kommo_update_lead. However, it could explicitly contrast with siblings to be a 5.

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 like kommo_update_lead or when to avoid it. The description lacks context about prerequisites or typical use cases.

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