Rename a layer

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

Annotations already mark this as readOnly=false and destructiveHint=true, so the description does not need to restate the mutation. It adds value by explaining the consequence: renaming affects generated code class names, making it a real change rather than cosmetic. No contradiction with annotations, but no further behavioral detail such as undo, required permissions, or effects on references.

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 two short sentences with no filler. The core action is front-loaded, and the second sentence adds important context without redundancy.

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 simple two-parameter rename tool, the description plus schema and annotations cover the essential facts: what it does, the key consequence, mutability, and parameter meaning. No output schema is needed for a rename operation. Could be slightly more complete with explicit mention of scope or return behavior, but it is largely sufficient.

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?

The schema documents nodeId, including an example and the fallback to the current selection. 'name' is left without schema description, but the tool description gives it meaning by explaining that names become class names in generated code. This partially compensates for the 50% schema coverage, though no format, length, or uniqueness constraints are mentioned.

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 ('Renames a layer') and the target resource, matching the title. It adds meaningful context by explaining that layer names map to generated code class names, which clarifies why the tool exists. However, it does not explicitly distinguish this from siblings, though no direct rename sibling exists.

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?

No guidance is provided about when to use this tool versus alternatives or when to avoid it. The note about generated code is a rationale for why the change matters, not a usage condition. An agent is left to infer the appropriate context solely from the name and title.

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