design_add_concrete_texture

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

With no annotations, the description carries the full burden but only describes appearance. It never says what the tool actually creates (a new layer? a fill?), whether it respects the 'index' stack position, whether it can be undone/removed, or whether 'seed' makes results reproducible. That is a substantial gap for an unannotated mutation tool.

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?

A single front-loaded sentence with no filler. It is efficient, though its very brevity is part of why behavioral context is missing rather than a model of completeness.

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?

All 7 params are optional and 100% documented, and no output schema exists, so an agent can call it with defaults. But for a mutation tool with zero annotations, the description should explain what gets created and how it lands in the layer stack; that is missing.

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 defaults for seed, color, index, opacity, pitting, variation and coarseness are already documented. The description only loosely echoes three of them ('coarse aggregate'≈coarseness, 'pitting', 'mineral flecks'≈variation) without adding format or interaction detail, so the baseline 3 applies.

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 pairs a specific verb ('add') with a concrete resource ('concrete/stone surface texture') and enumerates its visual signature (coarse aggregate, pitting, mineral flecks). That is enough to separate it from the sibling texture tools (design_add_paper_texture, design_add_noise_texture, design_add_washi_texture), though no sibling is named.

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 is only implied: an agent infers 'use this when you want a concrete/stone look.' There is no statement of when to prefer this over the other texture tools, nor any prerequisite or exclusion. Slightly better than no guidance because the visual traits do discriminate among siblings.

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