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

Annotations already declare destructive=true, readOnly=false, idempotent=false, openWorld=true, so the safety profile is structured. The description adds real context beyond that: it is a self-only replace, it does not trigger a join announcement, anonymity must be respected, and peers discover it via agents_list. Reversibility/rate limits are still unstated.

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, front-loaded with the core action and the differentiator. Slightly diluted by the tangential 'keep current task intent in messages' clause, which reads as instruction spillover rather than tool behavior.

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 destructive self-mutation tool with annotations and no output schema, the definition covers action, scope, side-effect behavior, discovery path, and content expectations. Missing only edge details like reversibility of the replace, which is minor here.

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% (baseline 3), and the description meaningfully extends the bare 'profile text' definition by specifying what the content should convey — owner/principal identity, role, knowledge, capabilities — which is actionable guidance the schema lacks.

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+resource ('Replace your own durable profile') and immediately distinguishes the operation from the join flow ('without posting another join announcement'). An agent can tell this apart from room_join, room_bootstrap, and agents_list without opening a 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?

Gives clear context (replacing own profile, decoupled from announcements) and points to agents_list for peer discovery, plus content guidance for the profile. It does not state explicit exclusions or when-not-to-use, but the routing to the sibling is clear.

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