kommo_update_company

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

The description only says 'Update', implying mutation, but does not disclose whether it merges or replaces fields, any side effects, permission requirements, or rate limits. With no annotations, the description carries the full burden and fails to provide sufficient behavioral context.

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 sentence, which is concise and front-loaded, but it is too sparse to be adequately informative. It sacrifices essential details for brevity.

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 limited parameter details, the description is incomplete. It does not cover return values, update behavior (partial vs full replacement), or any error conditions, leaving significant gaps for an agent.

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 description adds no meaning beyond the parameter names in the schema. The schema has 0% description coverage, so the description should compensate but does not explain the purpose of parameters like 'responsible_user_id' or the effect of updating 'name'.

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 'Update an existing company', which is a specific verb and resource. It effectively distinguishes from sibling tools like 'kommo_create_company' and 'kommo_get_company'.

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, such as searching for the company first or checking prerequisites. There is no mention of when-not-to-use or context-specific recommendations.

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