Manage Variables

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

Annotations include openWorldHint, implying possible side effects, but the description does not elaborate on behavioral traits such as state changes, reversibility, prerequisites, or constraints. The description only states the actions without discussing consequences or permissions.

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 very concise at one sentence. However, it could be slightly more structured, e.g., listing the actions explicitly. The ambiguous '(create/update router)' detracts from 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 (10 parameters, 3 distinct actions), the description lacks completeness. It does not map actions to required parameters or explain the workflow. An output schema exists, but the description should still provide context for action selection.

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 100%, so the baseline is 3. The description does not add additional meaning beyond what the schema provides. It does not explain which parameters are required for specific actions or provide examples.

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 identifies the tool's purpose: creating collections and variables, and setting their values/aliases. It uses a specific verb-resource structure (create/set). However, the phrase '(create/update router)' is ambiguous and could be clarified. It distinguishes from sibling tools like variable_delete and variable_list by focusing on creation and update actions.

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 like variable_delete or variable_list. The description does not mention scenarios or conditions for using this tool, leaving the agent without decision support.

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