lookdev_display_color

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

No annotations, so the description carries full burden. It does disclose the exact attribute written (primvars:displayColor) and that it is not a material assignment, which is genuinely useful behavioral scope. However it omits permission needs, reversibility, and whether the prim must already exist — a meaningful gap for a mutation with zero annotation coverage.

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; the key constraint is parenthesized right where it matters. Efficient, if extremely terse.

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 output schema exists so return values are covered, but with no annotations, 0% parameter documentation, and an ambiguous path/prim_path pair, an agent lacks what it needs to call this reliably. The description should at minimum clarify the two path parameters and the color format.

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 0% across three parameters and the description adds nothing to disambiguate them. Critically, 'path' and 'prim_path' are both undocumented strings with no stated distinction, and the 'color' array's expected length/format (e.g., RGB floats) is never given.

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?

States a specific verb (Set), a precise target attribute (primvars:displayColor), and a resource (USD mesh). The parenthetical '(not a full material)' scopes it away from material tools like lookdev_preview_surface, giving real differentiation, though it doesn't name a sibling explicitly.

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 '(not a full material)' clause implies when this lightweight override is appropriate versus a real material, but there is no explicit when-to-use, prerequisites, or named alternative. Usage is inferable but not spelled out.

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