move_layer_order

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

No annotations are provided, so the description must bear the full burden. It indicates mutation ('change draw order') and the before/after positioning, but does not disclose if the operation is reversible, any side effects, or prerequisites like layers being in the same group. The parenthetical 'map.moveLayer' is ambiguous and may confuse agents as to whether this is a Mapbox or ArcGIS tool.

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, front-loaded sentence that efficiently conveys the core action. It is concise but could be slightly improved by clarifying the tool's context (e.g., ArcGIS Pro).

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 has 6 parameters and an output schema is present, the description does not mention the output or what happens after the move (e.g., immediate effect, saving). It is adequate for a simple tool but lacks full context.

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%, so the description must compensate. It mentions three key parameters (layer_name, reference_layer, position implicitly via BEFORE/AFTER) but does not explain save, map_name, or aprx_path. The description adds marginal meaning beyond what is in the 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?

The description clearly states the verb 'change draw order' and the resource 'layer', specifying it moves a layer BEFORE/AFTER a reference layer. This distinguishes it from siblings like 'remove_layer_from_map' or 'rename_layer'.

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 provides no explicit guidance on when to use this tool versus alternatives. No context about prerequisites, when not to use, or comparisons with similar tools is given.

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