lightprobe.set

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

With no annotations, the description carries the full burden for behavior disclosure. It only states 'Set' implying mutation, but omits details like side effects, permissions, error handling, or reversibility. Insufficient for an AI agent to understand consequences.

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?

While the description is brief, it is under-specified. It sacrifices necessary detail for brevity, lacking structure like parameter explanations or example usage. Conciseness should not come at the expense of clarity.

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 no output schema, no annotations, and a moderate-complexity tool with 3 required parameters and many sibling tools, the description fails to provide sufficient context. An agent cannot reliably determine how to construct valid inputs or what the outcome will be.

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%. The description adds no information about the parameters beyond what the schema titles provide (name, value as JSON, property). For example, it does not clarify the format of 'property' or acceptable JSON structure. The agent must infer from the tool name and schema alone.

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), the resource (one RNA property), and the target (a light probe data-block). This is specific and distinguishes it from siblings like lightprobe.report or lightprobe.create.

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 on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or cases where other tools (e.g., rna.set_property) might be more appropriate.

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