manage_global_variable

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds context that variables are 'user-defined constants accessible in strategies,' which is helpful but does not disclose further behavioral traits such as impact on strategies or undo possibilities.

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 extremely concise: two sentences with no superfluous words. It front-loads the primary actions and provides a brief definition of the resource.

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, the description could include more complete context, such as the consequences of deletion or the requirement to provide 'id' for update/delete. While it covers the basic purpose, it leaves some operational details implicit.

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 the baseline is 3. The description does not add additional meaning to the parameters beyond what is in the schema (e.g., no explanation of how 'id' relates to 'action' or constraints on 'value').

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?

Description clearly states the tool performs create, update, or delete operations on global variables. The verb 'manage' plus the specific resource 'global variable' is unambiguous and distinguishes it from sibling tools that focus on bots, deals, and presets.

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 implies usage for managing global variables but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. Users must infer from the action enum.

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