app_set_var

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

Annotations already provide readOnlyHint=false, idempotentHint=true, and destructiveHint=falseikuha. The description adds 'LIVE' and the workspace scope, but it does not disclose important behaviors such as overwriting an existing variable, whether the variable must already exist, whether it is created if absent, or what the tool returns. No annotation contradiction is present.

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 a single short sentence that is front-loaded and contains no filler. The 'LIVE:' prefix is somewhat unexplained and may not contribute meaningful structure, but overall the entry is appropriately compact.

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 simple two-parameter setter, the description gives the basic action, but with no output schema and no usage guidance, an agent lacks context about return values, whether variable creation is implicit, and how this differs from add_variable. The available annotations do not cover these 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?

Schema description coverage is 0%, so the description must compensate for missing parameter detailsci. It does not define 'name' or 'value' beyond their obvious names, nor does it clarify value types, coercion behavior, or how 'global' affects interpretation of the name parameter.

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 uses the verb 'set' with the object 'a global variable in the app workspace', which clearly indicates a value-assignment operation. It is distinguishable from the sibling app_get_var (read), but it does not explicitly distinguish itself from add_variable, which could imply creating a 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?

There is no guidance about when to use this tool versus add_variable or app_get_var. The 'LIVE:' prefix hints at runtime context, but there are no explicit conditions, exclusions, or alternatives mentioned.

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