apply_procedural_texture

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

With no annotations, the description carries the full burden and does well: it discloses the AMS/MMU dependency, the side effect of opening an inline 3D stage, automatic decimation of oversized meshes, and a rate limit (3 textures/month, unlimited Pro). It stops short of explaining what happens to the source file or how save_to_library mutates state.

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 core purpose is front-loaded and the AMS/MMU condition is stated early. But the definition is padded with an upgrade URL and a separate 'INLINE 3D STAGE' section that restates the stage-opening behavior already mentioned in the first paragraph, wasting space.

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 23-parameter mutation tool with no annotations, no output schema, and 43% schema coverage, the description is materially incomplete. It never explains the bulk of the parameters, the return value, or the effect on the input mesh/design, leaving the agent without enough to invoke it confidently.

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 only 43% across 23 parameters, and the description adds essentially no parameter meaning — texture, preset, surface, num_colors, color_palette, mark_* and relief_* fields are all unexplained. With high param count and low coverage, the description should compensate but does not.

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 names a specific verb and resource ('Apply a multicolor procedural texture') and states the key precondition (AMS/MMU required). It clearly distinguishes the tool by name-implication from siblings like apply_image_texture and apply_geometric_texture, but never names or contrasts them explicitly, so differentiation is left to the reader.

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?

It gives a hardware prerequisite (AMS/MMU for multi-material) and quota context (3/month free, unlimited Pro), which implies usage context. However it never says when to prefer this over apply_image_texture, apply_geometric_texture, or auto_multicolor_from_texture, and provides no when-not guidance.

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