Update single company

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

The description adds no behavioral traits beyond the verb 'update'. Annotations indicate idempotency and open-world hints, but the description does not clarify whether the update is partial or full replacement, nor any side effects. It does not contradict annotations, but it adds minimal value beyond them.

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, front-loaded with the action 'Update', and contains no unnecessary words. It is effectively concise and well-structured.

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?

For a simple update tool, the minimal description conveys the core purpose, but it leaves gaps. The lack of detail about the `company` object format and the potential ambiguity with the sibling `kommo_companies_update` tool are not addressed. The annotations provide some context, but the description alone is adequate yet not comprehensive.

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 provides no information about the `id` or `company` parameters. With schema description coverage at 50% and the `company` object only vaguely described as 'Company object per Kommo API', the description does not compensate for the low coverage or explain how to construct the object.

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 action (update), the resource (company), and the scope (single by ID). This distinguishes it from the sibling tool kommo_companies_update, which likely handles bulk updates.

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 phrase 'single company by ID' implies it is for updating one entity, but it does not explicitly mention when not to use it or call out the alternative kommo_companies_update for bulk operations. The guidance is 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.