Set Layer Properties

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

Describes that only specified properties change, others remain. No contradiction with annotations (readOnlyHint false matches mutation). No side effects or limits described, but sufficient for a simple update.

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?

Two well-structured sentences. Front-loaded with purpose and partial update behavior. No filler.

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?

Satisfies needs for a 6-param tool with no output schema. Provides clear purpose, partial update, and inspection hint. Could mention active document, but not required.

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% (baseline 3). Description adds 'Only specified properties are changed; others remain' which clarifies partial update semantics beyond schema.

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?

Clearly states 'Update one or more properties on a layer' with specific verb and resource. Distinguishes from siblings by hinting at inspection via get_layers.

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?

Explicitly suggests using get_layers before modifying to inspect current values. Provides clear context for when to use this tool versus the inspection tool.

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