light_create_spot

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

The description adds behavioral details beyond the annotations, specifically that the light is placed at a given position while the target is auto-offset, and that cone angle and penumbra are adjustable. The destructiveHint annotation already flags that this is a mutating operation, so the description does not need to restate that.

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 short, bilingual, and front-loaded with the key purpose and behavior. It avoids redundant parameter enumeration while still giving the essential distinguishing details.

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 an 8-parameter creation tool with no required parameters and full schema coverage, the description covers the essential behavior and the distinctive auto-offset target trait. It does not mention return values or defaults, but the schema handles parameter documentation and no output schema is present.

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 100%, so the schema already documents all parameters. The description mentions cone angle and penumbra, which maps to coneAngle and penumbra, but does not add significant meaning beyond the schema's own parameter descriptions.

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 a specific action and resource: 'Create a Target Spot light at the given position with an auto-offset target.' This distinguishes it from sibling light-creation tools like light_create_omni, light_create_directional, and light_create_area.

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 makes it clear this tool is for creating a target spotlight, with an auto-offset target and configurable cone angle/penumbra. It provides useful context for when to use it, though it does not explicitly name alternatives or exclusion conditions.

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