set_global_variable

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

The description discloses that all bound dimensions rebuild automatically when a variable is updated. It also mentions the error case for non-existent variables. With no annotations, this fully covers behavioral traits.

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 well-structured with clear sections, but it includes both Spanish and English text for the same information, which adds slight redundancy. The key information is front-loaded.

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 3 parameters, no output schema, and no annotations, the description fully captures purpose, usage, parameters, behavior, and error conditions. It leaves no critical gaps.

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?

Although the input schema has no descriptions (0% coverage), the description explains each parameter in detail: `name` must exist, `new_value` is numeric with units, and `units` is optional with specific allowed values and preservation behavior.

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 it modifies an existing global variable, distinguishing it from `add_global_variable`. The verb 'modificar' and resource 'variable global existente' make the purpose explicit.

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?

It provides a typical usage example (CSWA workflow) and explicitly warns that the variable must exist, guiding the agent to call `add_global_variable` first. This tells when to use and when not to.

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