lightprobe-configure-lights

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

No annotations are provided, so the description bears full responsibility. It describes the action as 'batch-configure' and explains the parameter structure, but does not disclose potential side effects, atomicity, or whether the operation is destructive. Lacks explicit behavioral details beyond the core function.

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?

Three sentences covering purpose, parameter explanation, and usage prerequisite. No redundant information; every sentence serves a clear function. Front-loaded with purpose.

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 absence of output schema and annotations, the description adequately explains the tool's purpose and usage. References a sibling tool for context. However, it omits mention of return values or success/failure indicators, which could be helpful for an agent.

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 significant meaning beyond the schema by explaining that each entry specifies a name pattern with wildcard support and target mode, and lists allowed modes (Realtime, Baked, Mixed), while the schema only provides a brief example. Schema coverage is 100%.

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 'Batch-configure Light bake modes in the scene', specifying the verb (batch-configure), resource (light bake modes), and the action. It distinguishes from the sibling 'lightprobe-analyze' which is for inspection.

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 explicitly advises to 'Use lightprobe-analyze first to inspect all lights and their current modes, then decide which lights to change based on the analysis', providing clear guidance on when to use this tool and the prerequisite step.

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