shaderfx-set

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

With no annotations provided, the description must explicitly disclose behavioral traits. It only says 'set', which implies mutation, but does not mention side effects, error behavior, or any requirements (e.g., whether the shader effect must already exist, whether it overwrites existing values, or what happens on failure). The description is insufficiently transparent for a mutation tool.

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 sentence that is front-loaded with the verb and resource. It is efficient and avoids fluff, though it may be overly terse given the tool's complexity.

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 tool with 4 required parameters, no annotations, and no output schema, this description is critically incomplete. It does not explain how the shader effect is identified, what the value format is, or any operational context (e.g., that it mutates an existing effect). It leaves too much to the agent to infer from parameter titles alone.

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 description adds no information about the parameters beyond what the schema titles already provide. It does not explain the relationship between object/name/property/value, nor clarify that value is expected as a JSON string. Schema coverage is 0%, so 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 clearly states the action: set one RNA property on a shader effect. It uses a specific verb (set) and resource (shader effect), and distinguishes from sibling tools like shaderfx-add, shaderfx-remove, and shaderfx-report by focusing on property assignment.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as the shader effect needing to exist first, or contrast with shaderfx-set versus other set tools like shading-set_node_input or rna-set_property.

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