create_variable_collection

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

The description does not clarify why the tool is marked with destructiveHint=true. While it mentions the free plan limitation, it contradicts the annotation by only describing additive behavior. The openWorldHint is also unexplained.

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 concise with two sentences, front-loading the main action. The second sentence is lengthy but packs essential guidance without 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 description covers the free plan limitation and provides a workaround, but lacks details on return values, required permissions, or the implications of the destructive annotation. It is adequate but not fully comprehensive.

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 the schema already documents both parameters. The description adds minimal value by restating the optional initial mode name, but no format or constraints beyond what's in the schema.

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 a new local variable collection with an optional initial mode name, using a specific verb and resource. It distinguishes from sibling tools like add_variable_mode by explicitly mentioning when not to use that alternative.

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 explicit when-to-use and when-not-to-use guidance, naming the alternative tool (add_variable_mode) and offering a workaround for the free plan limitation. This is comprehensive.

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