apply_image_texture

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

With no annotations at all, the description carries the full burden, and it does disclose real behavior: a 3D stage opens on success, oversized meshes are decimated for the stage, and there is a hard free-tier cap of 3 textures/month with a Pro upgrade path. It omits key mutation details — whether the source mesh is modified in place or a new file is written, what formats input_path/image_path accept, and whether the call requires an authenticated account.

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 opening sentence is well front-loaded, but the uppercase INLINE 3D STAGE paragraph restates the same information already given in sentence one at roughly triple the length. The pricing link is justified by the quota mention but the overall block is padded.

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?

A 20-parameter mutation tool with no annotations and no output schema needs the description to cover where output goes, what the return looks like, and what the parameters mean. The description spends its budget on the viewer experience and pricing instead, leaving core call semantics undocumented.

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 a nominal 65%, but those schema descriptions are almost entirely 'Default: X' with no meaning attached, and several parameters (region, surface, tile_size_mm, angle_limit_deg, segmentation_params) have no description at all. The tool description explains zero of the 20 parameters, so an agent gets no help understanding mode vs style, what 'face: auto' selects, or how depth_mm and tile_size_mm interact.

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 first sentence names a specific verb and resource ('Apply a photo-based texture as a tiled deboss/emboss pattern'), and the qualifier 'photo-based' plus the image_path parameter implicitly separate it from the geometric/procedural texture siblings. It stops short of explicitly naming apply_geometric_texture or apply_procedural_texture as alternatives.

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: the agent can infer this is the tool for turning a raster photo into relief, and the free-tier quota (3/month) gives a practical constraint. There is no explicit when-to-use / when-not-to-use statement and no guidance on choosing between this and apply_geometric_texture or apply_procedural_texture.

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