Create Workspace Variable

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

Annotations indicate a mutating operation (readOnlyHint=false), and the description adds one extra behavioral detail: returned values are masked when secret or sensitive. However, it omits other relevant behaviors like idempotency, potential errors, or permissions. The masking note is useful but minimal.

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 exceptionally concise: two sentences that state the purpose and a key behavioral note. It's front-loaded and avoids redundancy, though it could elaborate on parameters or usage.

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 7 parameters with zero schema descriptions, the description provides almost no contextual guidance. It doesn't explain parameter semantics, required vs optional, or how workspaceId is used. While output is implicitly described, the lack of parameter context makes it incomplete.

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 input schema has 7 parameters with no descriptions, and the tool description provides no explanation of any parameter. With 0% schema coverage, the description completely fails to compensate, leaving key, value, isSecret, isEnabled, sortOrder, description, and workspaceId unexplained.

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 the action: 'Creates one workspace-global variable' with the specific verb 'creates' and resource 'variable'. It distinguishes itself from sibling tools like update_variable and delete_variable by the explicit creation action, though it does not explicitly differentiate from replace_variables.

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?

No guidance on when to use this tool versus alternatives like update_variable or replace_variables. The description provides no context about prerequisites, scenarios, or when not to use it, leaving the agent to infer from the tool name alone.

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