Set System Variable

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

Adds type auto-detection behavior beyond annotations. However, fails to mention the confirm parameter's role in authorizing protected targets, which is a significant behavioral trait not covered by 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?

Single sentence, no fluff, front-loaded with action and key detail (type auto-detection). Highly concise.

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 the destructive hint and presence of confirm parameter, the description is incomplete—should explain the confirm parameter's effect. Adequate for basic usage but misses important safety context.

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 coverage is 100%, so baseline is 3. The description adds value by noting type auto-detection for the value parameter, but does not explain the confirm parameter beyond the schema.

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 sets a system variable value, distinguishing it from create/delete siblings by implying modification of existing variables. However, it could more explicitly differentiate from create_system_variable.

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 advises using list_system_variables to see available variables, providing some context for usage. But no explicit when-not-to-use or alternatives among siblings are given.

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