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

Annotations only flag destructiveHint=true and idempotentHint=false generically; the description goes further by disclosing that claiming is a one-time, irreversible act after which the handle is permanent, that reserved/taken handles are rejected, that mutation actions need a verified email, and that a provisional `maker-...` handle is renamed by claim. This is exactly the beyond-annotation context needed for an irreversible write.

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 dense paragraph that front-loads what the resource is, then walks get/claim/update in order with no filler sentences. It is on the long side for one paragraph but each clause carries a constraint or behavior, so little is wasted.

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, the description usefully states what get returns (handle, claimed status, tenure, rating and template counters) and covers prerequisites and permanence for the mutations. Minor gaps remain, such as the shape of responses for claim/update and error behavior, but nothing critical for correct invocation is missing.

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 bio, url, action, handle, and display_name, including the regex and length limits. The description largely restates those constraints (lowercase 3-to-32-character handle) and adds only the provisional-handle rename nuance, so 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?

It names a specific resource (the caller's community publisher identity/@-handle) and enumerates three concrete actions with their effects (get returns the profile; claim sets the handle once; update changes display_name/bio/url). An agent can distinguish this tool's scope from every sibling in the list 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?

The description ties each action to its preconditions: claim may be used only once and requires a verified email, update also requires a verified email, and claim refuses reserved or taken handles. It doesn't explicitly say when to prefer get vs update, but the action semantics make the choice self-evident, so this is clear context without formal exclusions.

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