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

Goes well beyond the annotations by disclosing the cascade behavior (projects carrying it and rules matching it follow the new name), the important safety fact that access does not move, the refusal-on-collision rule, and the permission requirement. The destructiveHint=true annotation is consistent with a rename that changes a global tag name, and the description supplies the operational context the annotations cannot.

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 tight sentences: action first, then behavioral consequence, then the exclusion and permission. Every sentence carries distinct, non-redundant information with no filler.

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?

With no output schema and only two fully described parameters, the description covers everything an agent needs: what changes, what does not, the failure condition, the alternative tool, and the authorization requirement. Nothing material is left unstated for this operation.

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 coverage is 100%, so both parameters and their formats (including 'exactly as list_tags returned it') are already documented. The only added semantic is the constraint on `name` that it must not collide with an existing tag, which is useful but marginal against a fully documented 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?

States a specific verb (rename) and resource (tag) and immediately positions it against the sibling merge_tags, which is the closest alternative. An agent can distinguish rename_tag from create_tag, delete_tag, and merge_tags without opening any 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?

Explicitly names the exclusion case (renaming onto an existing tag is refused) and routes to the correct alternative (merge_tags combines two tags), plus states the required role (Owner and Admin). It stops short of spelling out when to prefer renaming over delete/recreate, so it is clear context rather than a full when/when-not contract.

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