design_add_parchment_texture

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

No annotations exist, so the description carries the full behavioral burden. It never states whether this creates a new layer or modifies an existing one, what 'index' stack position means operationally, whether the effect is non-destructive/adjustable, or whether a selection is required.

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 efficient sentence with no padding, and the defining traits are front-loaded after the verb. It is appropriately sized, though it spends its words on appearance rather than the routing information an agent actually lacks.

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?

An eight-parameter texture generator with no annotations and no output schema needs more than one sentence. Nothing explains layer behavior, stacking via 'index', interaction with opacity/blend, or how to pick this over the other texture tools.

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 all eight parameters are already documented with ranges and defaults. The description's mention of foxing spots, staining, and edge darkening loosely maps to foxingDensity, stainIntensity, and edgeDarkening, adding only light semantic reinforcement rather than new information.

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?

Specific verb ('Add') plus a specific resource ('aged parchment/vellum texture') with three named visual characteristics. An agent can tell this is a parchment texture generator, but it never names the adjacent siblings (design_add_paper_texture, design_add_washi_texture, design_add_linen_texture) that an agent must choose between.

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 contains no when-to-use, when-not-to-use, or alternative guidance, despite six near-identical texture siblings in the tool list. The choice between parchment, paper, vellum, washi, linen, and concrete is left entirely to inference from the material name.

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