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

With destructiveHint=true and idempotentHint=true already declared, the description adds genuine value by enumerating what is preserved — passwords, settings, retention, human ownership — which bounds the blast radius of a hint-flagged mutation. It does not mention that the previous name is replaced/lost or what the response looks like.

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?

Two sentences, no filler, with the authorization scope front-loaded and the side-effect boundary immediately after. Every clause earns its place.

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 two-parameter mutation with full annotation coverage and no output schema, this is nearly complete: authorization scope and preserved state are both covered. What is missing is failure behavior (expired grant, invalid name) and any hint about the returned result.

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 50%: room_id is documented by the schema, but name carries only length bounds with no prose anywhere. The description implicitly constrains room_id to rooms where the agent holds a manager grant, which is useful, but adds nothing about name content or constraints.

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 and resource ('Renames the room') and narrows scope to the room covered by this agent's live room-only manager grant, which separates it from creation siblings like create_room/add_room. It never names an alternative tool explicitly, 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?

Usage is implied rather than stated: the caller must hold a live room-only manager grant on that room, which is a real precondition the description surfaces. There is no explicit 'use this when X, not Y' routing or statement of what happens if the grant is absent or expired.

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