create_variable_collection

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

Basic information: creates a collection with modes. No details on side effects, permissions, or success/failure responses. With no annotations, the description carries the burden but adds little beyond schema.

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?

Single sentence, no fluff. Could be slightly more structured (e.g., separate parameter details), but concise and to the point.

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?

Adequate for a simple creation tool, but lacks explanation of what a 'collection' is in the context of design tokens and how it relates to variables. No output schema, so return behavior is ambiguous.

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 is 3. Description adds 'design token collection' context and example ('Light/Dark'), but does not clarify parameter constraints, uniqueness, or special values beyond 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?

Includes specific verb 'Create' and resource 'design token collection', with mention of modes. Distinguishes from siblings like create_variable (single variable) and update_variable, but could be more explicit about what a collection encompasses.

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 over alternatives (e.g., create_variable for individual tokens, create_design_tokens for bulk). No context about prerequisites or typical use cases.

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