Create or update a design token

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

Description expands on annotations (idempotentHint=true) by clarifying it writes file in place and returns creation timestamp. Also documents validation behavior per type. No contradiction 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?

Two sentences: first sentence states core purpose, second adds validation and return details. Every sentence adds value with no 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?

Describes return shape and validation constraints. Lacks error handling details but is sufficient for a simple upsert tool without output schema.

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 covers 100% of parameters, but description adds concrete examples (e.g., '#0F766E', '32px') and validation rules per type, helping the agent format values correctly.

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?

States 'Create or update a design token' with specific verb and resource. Explicitly distinguishes from siblings: 'This is the only tool in this server that modifies the token file.'

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 explicit when-to-use or when-not, but identifying it as the only modifying tool implies usage for token mutations. Also specifies validation rules to guide correct usage.

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