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

Annotations declare destructiveHint=true and non-idempotent, and the description adds real value beyond them by disclosing that the new design is blank, inherits no artwork, and that the advanced replaceDesigns:true flag replaces the session design collection. That replacement warning is exactly the kind of destructive consequence the agent needs.

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?

Three short sentences, front-loaded with the core action and inheritance caveat, followed by the advanced replace warning. Nothing is redundant.

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 essentials for a destructive, nested-parameter mutation with no output schema: what it creates, what it does not inherit, and the collection-replacement side effect. It could still be clearer about what is returned, but annotations plus the options description carry most of the load.

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 the schema already documents all four parameters, making 3 the baseline. The description only loosely maps to the options fields (product, colour, size, quantity, print areas) and introduces the undocumented replaceDesigns flag, adding marginal meaning.

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 a specific verb and resource ('Create another independent blank design in this session') and distinguishes it behaviorally from related tools by noting it does not inherit artwork from the active design. It does not name sibling alternatives like create_design_variants or load_design, so it stops short of a 5.

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?

Usage context is only implied: it is for adding a fresh blank design in an existing session. There is no explicit 'use this instead of X when...' guidance against the many sibling design tools, though the 'does not inherit artwork' line helps rule out copying scenarios.

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