Initialize Design Project

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

Annotations indicate destructiveHint=true and readOnly=false. The description adds context by specifying that previous state is cleared and a complete token set is generated, plus the real-time dashboard update. This is useful behavioral information beyond the 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?

The description is well-structured with a main statement, a side-effect note, an Args list, and examples. It is reasonably concise for a tool with 3 parameters, though it does repeat schema details. The primary purpose 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?

The description covers core purpose, side effects, parameters, and examples. It does not describe the return value, but given the absence of an output schema and the presence of design_get_state among siblings, this is acceptable and fairly complete.

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?

The schema covers all parameters with descriptions. The description repeats parameter names/types and includes examples with concrete values, but adds little new semantic meaning since the style enum and base_color hex format are already 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 initializes a new design project, sets style, generates a token set, and clears previous state. This distinct purpose separates it from sibling tools that update or add specific components.

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 implies use for new projects ('Initialize a new design project') but provides no explicit alternatives or exclusions. It hints at starting fresh ('clears any previous state'), yet does not compare to design_set_theme or design_generate_design_tokens.

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