create_variable

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Create a variable' implies a write/mutation operation but provides no information about permissions required, whether the operation is idempotent, what happens if a variable with the same key already exists, rate limits, or what the response looks like. This leaves the agent with critical gaps in understanding how to properly invoke this tool.

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 maximally concise at just two words, with no wasted language or unnecessary elaboration. While this conciseness comes at the cost of completeness, the description is perfectly structured in its brevity and gets straight to the point without any filler content.

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 that this is a mutation tool with no annotations, 3 parameters (2 required), 0% schema description coverage, and no output schema, the description is completely inadequate. A proper description for this context would need to explain what system the variable belongs to, what the parameters mean, what happens on success/failure, and how this differs from sibling variable tools. The current description provides none of this essential 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?

The description provides zero information about the three parameters (key, value, description) despite the schema having 0% description coverage. The agent must infer from the parameter names alone what these represent and how they should be used. For a creation tool with multiple parameters, this represents a significant documentation gap that the description fails to address.

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 'Create a variable' is a tautology that merely restates the tool name without providing any meaningful context about what kind of variable is being created, in what system, or for what purpose. While it does contain a verb ('Create') and resource ('variable'), it lacks the specificity needed to distinguish this from other variable-related tools like 'update_variable' or 'delete_variable' in the sibling list.

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 provides absolutely no guidance on when to use this tool versus alternatives. There are multiple sibling tools dealing with variables (create_variable, delete_variable, get_variable, list_variables, update_variable), but the description offers no context about when this specific creation tool should be selected over other variable operations or what prerequisites might be needed.

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