Manage Variables

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

The description correctly identifies the tool as creating/updating, and annotations include openWorldHint. However, it does not disclose that the tool handles multiple action types (create collection, create variable, update variable) or that some parameters are conditionally required. No contradictions with 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?

The description is a single sentence with no extraneous content. It is efficient but could be more structured to separate the different actions for clarity.

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 tool's complexity (11 parameters, three action types) and openWorldHint, the description is too brief. It does not explain the expected behavior for each action, return values, or dependencies between parameters, leaving significant gaps for an AI agent.

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 3 applies. The description adds minimal context by mentioning 'values/aliases', but does not elaborate on parameter roles beyond what the schema already provides.

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 tool creates/updates collections and variables, distinguishing it from siblings like variable_list and variable_delete. However, the parenthetical '(create/update router)' is slightly confusing but does not obscure the main purpose.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when to use specific actions, or when to prefer sibling tools like variable_delete or variable_list.

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