lightprobe-set

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

With no annotations, the description must fully disclose behavior. It reveals that the tool mutates state ('Set'), but gives no information about side effects, error handling, reversibility, or prerequisites. The agent is left blind to what happens on invalid input or partial changes.

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, front-loaded sentence with no redundant words. It efficiently conveys the core operation.

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?

The tool is a simple setter, but with no annotations, no output schema, and minimal parameter documentation, the description is too sparse. An agent would need external knowledge about light probe data-blocks, RNA property paths, and valid values to use it correctly.

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 description coverage is 0%, so the description must compensate. It only adds the term 'RNA property', which hints at the property parameter's nature, but does not explain how to construct the value JSON, what names are valid, or how to find available properties. The schema titles already provide basic meanings, so the description adds marginal value.

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') and the resource ('one RNA property on a light probe data-block'). It is specific enough to distinguish from sibling tools like lightprobe-list or lightprobe-report, though it does not explicitly differentiate from other property-setting tools.

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, when not to use it, or how to discover valid properties. The description only states what it does, not the context in which it should be invoked.

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