art.detail.texture

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

Annotations are not provided, so the description carries the full burden of behavioral disclosure. It says 'Apply' but does not reveal whether the texture overlays, replaces, or blends with existing canvas content, whether the operation is reversible, whether it affects the whole session, or what the return value is. This is insufficient behavioral context for a mutating operation.

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 a single concise sentence with no filler and the key action is front-loaded. It earns its place by naming the operation and the target region in an immediately understandable way.

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?

For a 9-parameter tool with all parameters required, no annotations, and no output schema, this description is too thin. It omits the relationship to the art.detail workflow, whether this is a destructive edit, whether coordinates are canvas-absolute or relative, and what effect the density/seed parameters have on behavior. The schema helps with parameter meaning, but the contextual frame is incomplete.

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 already documents all nine parameters with meaningful descriptions, including pattern name value examples, region geometry, colors, density, seed, and session_id. With 100% schema description coverage, the tool description need not add much; however, it adds essentially no supplemental parameter semantics beyond 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 action ('Apply'), the resource ('a texture pattern'), and the target ('a rectangular region on the canvas'). It is specific enough to understand the tool's core function, but it does not explicitly differentiate this tool from sibling art.detail.* tools such as grain, crack, or speckle, which may also apply localized patterns.

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?

There is no guidance about when to use this tool versus alternatives like art.detail.speckle, art.detail.crack, art.detail.grain, or art.canvas.draw_noise. The description offers no usage context, no exclusions, and no conditions, so an agent must infer selection from the name and parameter list alone.

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