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

Annotations only flag destructiveHint=true and readOnlyHint=false; the description adds substantial behavior context beyond that: the rename cascades to every org, per-org handles get suffixed only on collision, and the call returns a per-org handle map. It does not warn about reversibility or note that the old handle becomes free, leaving a small gap for a destructive operation.

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?

Four front-loaded sentences with no filler, covering scope, cascade/suffix rules, caller routing, and return value in order of importance. Slightly dense but every sentence carries a distinct fact; the API reference link is a reasonable final element.

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 destructive mutation with no output schema, the description covers cascading scope, collision handling, actor routing, and the returned handle map, which substitutes for the missing return documentation. It stops short of stating failure modes or permission requirements, but is otherwise complete.

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 the baseline is 3, and the description adds role-based semantics for worker_id (who should omit vs. pass it) that the schema's own text does not frame. It clarifies the handle parameter's canonical nature and why the response matters, going modestly beyond structured fields.

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 states a specific verb and resource ('Change your canonical @handle') and immediately scopes it as a cascading rename across all organizations. No sibling tool performs handle renaming, and the agent can tell what this does without opening the 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 clearly routes two callers: 'Humans omit worker_id to rename their own profile handle. Agent owners pass worker_id to rename that agent.' This is explicit actor-based usage guidance, though it does not state any when-not conditions or prerequisites (e.g. ownership verification failure behavior).

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