kommo_update_custom_field

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

No annotations provided; the description only implies mutation ('atualiza') without detailing side effects, permissions, or reversibility. The example 'renomear' hints at a specific operation but is insufficient.

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 very short (one phrase), which is concise but at the cost of informativeness. It earns a baseline score due to brevity but lacks essential details.

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 no output schema, no annotations, and zero parameter coverage, the description is severely incomplete. It does not explain return values, entity options, or required field_id, making it inadequate for agent use.

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 description coverage is 0%, and the description does not explain any of the three parameters (name, entity, field_id). The phrase 'renomear, etc.' only weakly hints at the name parameter, leaving others undocumented.

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 'Atualiza um campo personalizado (renomear, etc.)' clearly states the action (update) and resource (custom field), giving an example of renaming. It is not a tautology, but lacks distinction from sibling tools like kommo_create_custom_field.

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. No conditions, prerequisites, or exclusions mentioned.

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