delimit_design_extract_tokens

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

Details side effects: read-only scan, auto-activation of Figma API based on token presence, calls backend function, and coercion of token_types via _coerce_list_arg. Since no annotations exist, the description fully discloses behavior.

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 four main sections: action, when to use, when not to use, and side effects. Every sentence adds value, and the most important information is front-loaded.

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?

Given the presence of an output schema (context indicates true), the description does not need to explain return values. It covers purpose, usage, and side effects adequately. Minor gap: no mention of error handling or empty results, but the output schema likely addresses this.

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. The description adds context about token_types values and coercion, but does not significantly extend meaning beyond the schema for figma_file_key or project_path.

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 'Extract design tokens from a project's CSS/SCSS/Tailwind config.' This is a specific verb (extract) and resource (design tokens from specific file types), and it later distinguishes from sibling tools like delimit_design_generate_tailwind.

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?

Explicitly provides 'When to use' and 'When NOT to use' sections, naming alternatives such as delimit_design_generate_component and delimit_design_generate_tailwind. Also includes a 'Sibling contrast' paragraph for differentiation.

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