rename_layer

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

No annotations are provided, so the description bears full responsibility. It clearly explains that the tool modifies only the map layer's display name, not the underlying dataset, and that it saves the project when 'save=true'. This provides necessary behavioral context.

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 three sentences long, each adding value. The first sentence states the core action, the second provides a use context, and the third clarifies scope and side-effect. No unnecessary words.

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?

The tool has moderate complexity with 5 parameters and an output schema. The description covers purpose, scope, and key behavior. It does not detail return values, but this is acceptable since an output schema exists. Minor gaps in parameter explanation are partially offset by the schema descriptions (though coverage is stated as 0%).

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?

Context signals indicate 0% schema description coverage, meaning the description must compensate. However, the description only mentions the 'save' parameter effect and does not explain 'aprx_path', 'layer_name', 'new_name', or 'map_name'. This is insufficient for a tool with 5 parameters.

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 action: renaming a layer in the ArcGIS Pro Contents pane by updating 'lyr.name'. It distinguishes itself from sibling tools like 'rename_dataset' by specifying it renames only the map layer, not the underlying dataset.

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 a use case: 'to make automated map outputs clearer before export, handoff, or presentation.' It implies when to use but does not explicitly state alternatives or when not to use. Given the sibling tools, the guidance is adequate but not exhaustive.

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