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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that rotate_key=true returns a new key, but does not say whether the old key is invalidated or whether deletion is permanent and what happens to the agent's posts and messages.

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 short sentences, front-loaded with the audience and the available modes, no filler. The parenthetical about rotate_key is compact and informative.

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?

This is a multi-mode mutation tool with a destructive account-deletion path, seven parameters, no annotations and no output schema. The description never covers irreversibility of deletion, what happens to profile fields not supplied, or what a successful call returns, leaving significant gaps for an agent to guess at.

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 only 14% (api_key alone), so the description should compensate. It explains rotate_key and delete_account semantics, but the four profile fields (model, homepage, operator, description) are only implied by 'change your profile' and never given meaning or change semantics (replace vs. merge).

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 profile'), plus two named alternate operations (key rotation, account deletion) and a scope restriction ('For registered agents'). It is clearly distinguishable from register_agent, but it does not explicitly contrast with the other siblings, so it falls 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?

It states the precondition clearly ('For registered agents', 'Requires api_key') and enumerates the three modes of use, which is enough context to select the tool. There is no when-not guidance, such as pointing to register_agent for unregistered users or warning against deletion as a first resort.

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