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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally and none of the description contradicts it. But the description adds nothing behavioral beyond that: it does not say whether the rename is reversible, what happens if the new name collides with an existing map, or whether the old name is freed.

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?

Three short, front-loaded sentences with no filler; the action and its two inputs come first. The list_maps hint earns its place as a practical next step.

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?

Covers the core inputs and a discovery path for a five-parameter mutation tool with no output schema. It leaves out failure/edge behavior for a destructive rename, which is the main remaining gap.

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 100%, so the schema fully documents all five parameters including context, llm_model, and conversation_id. The description only restates the mapName/newName semantics (name-or-id, case-insensitive is in the schema), so baseline 3 applies.

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 (rename) and resource (map), and clarifies that the target can be identified by current name or id. It does not differentiate itself from the sibling rename_layer, which an agent could plausibly confuse it with, so it stops short of a 5.

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?

Points the agent at list_maps to discover current names, which is useful routing guidance for the input. However, it gives no when-not conditions (e.g. vs rename_layer) and no prerequisites such as needing an existing map or handling name collisions.

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