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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value beyond them by warning that pointing base at an un-merged version would undo post-branch work, and by stating 'nothing checks that the changes really are in - that is up to you' – a non-obvious caveat about the tool's trust model.

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?

Purpose is front-loaded in the first sentence, followed by the merge/base interaction and the caveat. Three sentences with no filler, though the middle sentence is dense and could be split for readability.

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 six-parameter mutation tool with no output schema, the description covers the highest-risk behavior (base reassignment and its interaction with merge_feature) and the lack of validation. It omits what happens to unrelated fields on update and any permission requirements, but the critical operational context is present.

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 already documents all six parameters, making 3 the baseline. The prose loosely maps to base and the self-description fields but adds no naming, format, or validation detail beyond what the schema provides.

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 opening sentence names the specific verbs and fields: rename, change its self-description, and move its base. It explicitly distinguishes itself from merge_feature, so an agent can tell which tool owns the merge versus the attribute-edit operation without opening either schema.

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 gives the crucial prerequisite for the risky path: bring the newer version's changes into the feature before moving base, and implies merging is merge_feature's job. It does not spell out when a plain rename is preferable to change_code or other edit siblings, so guidance is clear but not exhaustive.

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