Actualizar variables de una llamada (CDR)

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's mention of 'escribe' (writes) adds minimal value. The description does not detail that previous values are overwritten or that the operation is irreversible, which would provide useful context beyond 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 consists of two concise sentences with no wasted words. It front-loads the action and adds a utility statement, making it easy to scan and understand.

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 tool with two parameters, one nested, and no output schema, the description is reasonably complete. It covers purpose, typical use, and parameter examples. However, it lacks details on the impact of the operation (e.g., whether variables are appended or replaced) and does not describe the 'callId' parameter in depth.

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 50% (only 'vars' is described). The description adds context for 'vars' (e.g., 'var1…var5 u otras') but does not explain 'callId' beyond its type. An example is given for 'vars', but semantic details for 'callId' (e.g., format, source) are missing.

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 verb 'escribe' (writes) and the resource 'variables/etiquetas sobre el registro de una llamada' (variables/labels on a call record). It also provides a concrete use case for classifying calls, which distinguishes it from sibling tools that update different resources (e.g., extensions, contacts).

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 indicates when to use the tool ('útil para clasificar llamadas') but does not explicitly mention when not to use it or provide alternatives. However, the context is clear and no conflicting sibling tools exist for the same purpose.

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