Paste Layer Properties

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

Annotations already declare this is a non-destructive, idempotent mutation (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds a valuable behavioral constraint not in annotations: that ALL is prohibited and only explicit categories may be applied. It does not say what happens to properties on the target that are not in the list.

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 compact sentence with the core action front-loaded and the prohibition appended. No filler, though it is terse enough that some needed detail is omitted rather than trimmed.

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?

An output schema exists so return values need not be described, and annotations carry the safety profile. But for a 6-parameter, all-required mutation with 0% schema coverage, the description does not explain the source/target path arguments or the pairing of map and layer identifiers, leaving notable gaps.

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 0% across 6 required parameters. The description clarifies only the 'properties' array semantics (explicit categories, ALL forbidden) and leaves aprx_path, source/target map names, and layer identifiers undocumented in both schema and description.

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 names a specific verb+resource (copy layer properties) and clarifies the scope via 'explicit semantic categories' with concrete examples (POPUPS, DISPLAY_FILTERS, SYMBOLOGY). This distinguishes it from sibling mutation tools like update_layer_cim or apply_symbology_from_layer, though the source→target paste semantics implied by the params are not spelled out.

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?

It states which property categories are valid and that ALL is forbidden, which effectively guides input selection. However, it gives no when-to-use context relative to alternatives and no prerequisites, so usage is implied rather than explained.

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