Set design system

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

Discloses that it writes tokens.json + design/*.md and returns a TOKEN CONTRACT. Without annotations, this provides good insight, but lacks details on destructiveness (overwrites?) or permission requirements.

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, front-loaded with the core action, efficient. Could include the exclusivity constraint, but still concise and informative.

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?

Covers the two usage methods and return value, but lacks clarity on exclusivity of presetId/customTokens (schema allows both) and the meaning of 'lock.' Useful 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?

Adds meaning beyond the input schema: explains the OR logic between presetId and customTokens, provides examples for overrides and customTokens. Schema coverage is 67% and description compensates with usage context.

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's purpose: 'Lock the design system.' It specifies the two usage modes (presetId with overrides OR customTokens) and distinguishes from siblings by referencing pixl_list_presets for presets.

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?

Provides explicit guidance: use presetId from pixl_list_presets with optional overrides, or customTokens for bespoke systems. Does not explicitly state when not to use, but the reference to pixl_list_presets implies it for listing presets.

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