setLayerMaterialOptions

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

No annotations are provided, so the description carries the full behavioral burden. It implies mutation but says nothing about whether all 16 parameters must be supplied, whether omitted properties are preserved, permission requirements, or reversibility/undo behavior — significant gaps for a setter with zero annotation coverage.

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?

A single front-loaded sentence that leads with the verb and resource before the property list. It is appropriately sized, though the trailing enumeration is somewhat redundant with the schema.

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 a 16-parameter mutation tool with no annotations and no output schema, the description is too thin: it omits partial-update behavior, the 3D-layer precondition, and any pointer to getLayerMaterialOptions for reading current values. The schema covers parameter detail but the description leaves the operational context incomplete.

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 100% and every parameter has its own description with units and ranges, so the schema does the heavy lifting. The parenthetical list in the description largely duplicates parameter names already documented in the schema rather than adding new meaning (defaults, interactions, or partial-update semantics).

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 states a specific verb (Configure) and resource (3D material options and shaders on a 3D layer), and enumerates the affected properties, so an agent can identify the operation. It does not, however, distinguish itself from the obvious sibling getLayerMaterialOptions or other layer-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?

There is no guidance on when to use this tool versus alternatives such as getLayerMaterialOptions or setLayerProperties, and no stated prerequisites (e.g. that the layer must already be a 3D layer). The agent must infer the context entirely.

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