update-lights

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

Without annotations, the description fully bears the behavioral transparency burden. It discloses that updates are partial ('patches only the fields you pass'), unresolved ids are reported, and the tool is GM-only. It also explains internal nesting of emission fields and provides examples like torch flicker.

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, efficient paragraph that front-loads the main purpose. Every sentence adds value, covering scope, partial update behavior, error handling, and permissions without redundancy.

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 tool's complexity (many parameters) and no output schema, the description is thorough. It lists all editable aspects and explains behavior. It lacks explicit return value info, but the partial update and error reporting context suffices.

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?

With 100% schema coverage, the baseline is 3. The description adds semantic value beyond the schema by providing real-world examples ('warm torch', 'add torch flicker'), explaining default values (alpha ~0.3), and clarifying the behavior of partial updates and darkness ranges.

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 'Edit one or more placed AMBIENT LIGHTS by id' with specific editable fields like x/y, dim, bright, color, etc. It distinguishes from sibling tools like create-lights and delete-lights by mentioning 'update' and referencing 'list-lights'.

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 implies usage after listing lights and for updating existing lights. It provides context on partial updates and GM-only access, but does not explicitly state when not to use it or mention alternatives like create or delete.

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