RenameTag

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact — the rename propagates to every place the tag is used — but says nothing about auth requirements, failure modes (e.g. name collisions beyond the schema note), or side effects on tagged items.

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?

A single eight-word sentence with the action and its scope front-loaded. Nothing is padded or redundant.

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 an output schema present, a fully described input schema, and annotations covering the safety profile, the description only needs to convey scope — which it does. The remaining gap is the absence of any when-to-use routing against sibling tag tools.

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 tag_id and name are already fully documented, including the uniqueness constraint and a pointer to ListTags. The description contributes no additional parameter detail, so the 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 (tag), plus a scope qualifier ('everywhere it's used') that meaningfully distinguishes it from Matter_AddTag, Matter_RemoveTag and Matter_DeleteTag. It does not name a sibling explicitly, so it falls just 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?

There is no guidance on when to choose this over Matter_AddTag or Matter_DeleteTag, nor any prerequisite context. Usage is only implied by the verb, which is the minimum for a rename tool surrounded by other tag operations.

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