create_variable_collection

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

No annotations are provided, so the description carries the full burden. It discloses the 'local' scope and the behavior of mode names (first renames default, rest added). However, it does not mention permissions, irreversibility, return values, or error conditions, which are relevant for a create 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 two sentences: the first states the purpose, and the second explains the optional modes. Every sentence contributes meaningfully, with no unnecessary detail or redundancy.

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?

The tool is simple with only 2 parameters and no output schema. The description covers the essential behaviors, including the subtle mode-handling logic. While it lacks mention of return values and safety implications, the description is adequate for a straightforward create operation.

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% with descriptions for both 'name' and 'modes'. The description's statement about modes duplicates the schema's parameter description without adding new information. Thus, it provides no additional semantic value beyond what the schema already offers.

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 'Create a local variable collection' with a specific verb (create), resource (variable collection), and scope (local). It distinguishes from sibling tool create_variable by targeting a collection rather than a single variable. The additional detail about mode names reinforces the 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?

The description provides clear context for when to use the tool by naming the resource and explaining the optional modes behavior. However, it does not explicitly state alternatives or exclusions, such as 'use create_variable for individual variables'. Still, the purpose is specific enough to imply its usage.

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