layer_setProperties

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing about whether unspecified properties are left untouched, whether changes are reversible, whether the target layer must exist, or whether undo grouping applies. 'Set' implies mutation but no mutation semantics (permissions, side effects, return behavior) are described.

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?

It is a single front-loaded sentence with no padding, which is good, but the 'etc.' is hedging that wastes the one slot where useful enumeration could have gone. Brevity here comes at the cost of specification rather than being earned conciseness.

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 5-parameter mutation tool with zero annotation coverage, no output schema, and only 20% parameter description coverage, this one-liner is far too thin. An agent cannot determine required inputs, mutation semantics, or the full set of controllable properties from the description.

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 only 20% – just document_id is documented in the schema. The description names 'visibility' and 'lock' (mapping loosely to visible/locked) but ignores the required layerIndex and the printable property, and adds no format or default details beyond what the schema shows. It does not compensate for the low coverage.

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?

States a specific verb and resource ('Set layer properties') and gives two concrete examples (visibility, lock), which is enough to distinguish it from siblings like layer_create, layer_list, layer_delete, and layer_reorder. However, the trailing 'etc.' leaves the actual scope of settable properties ambiguous and omits the 'printable' property that the schema exposes.

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 offers no when-to-use guidance, no mention of prerequisites such as needing an open document or a valid layerIndex, and no differentiation of when to prefer this over layer_create or layer_reorder. An agent must infer everything from the tool name alone.

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