shaderfx.set

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

The description implies a mutation but does not disclose side effects, permissions, or error behavior. With no annotations, the description carries the full burden, and it fails to mention whether the operation is reversible or requires specific access.

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 extremely concise (one sentence), but this brevity sacrifices necessary detail. It is not excessively long, but it lacks completeness while still being direct.

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?

Given the lack of annotations, no output schema, and 0% parameter documentation, the description is woefully incomplete. It does not explain return values, error handling, or parameter interactions, leaving the agent underinformed.

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 has 0% description coverage, yet the description adds no meaning to the parameters. It does not explain the difference between 'name' and 'object', nor the expected format of 'value' as JSON. The description offers no value beyond the parameter names in 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 it sets one RNA property on a shader effect, which is a specific verb-resource combination. It distinguishes from sibling tools like shaderfx.add (add effect) and shaderfx.report (read).

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 description provides no guidance on when to use this tool versus alternatives like shaderfx.report for reading or shaderfx.remove for deletion. There is no mention of usage context, prerequisites, or exclusions.

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