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

Annotations already declare this tool as non-read-only and destructive, but the description adds useful behavioral context: destructive account/personalization actions require confirmation and an explicit request, webhooks are signed and gated by paid plans, and preferences include provenance. These details go beyond the structured annotations. The omission of `revoke_key` behavior keeps it from a 5.

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?

The description is a single semicolon-separated sentence that is front-loaded with the view operation and then groups related actions. It is dense but efficient, with no filler. A clearer enumeration of actions, especially including `revoke_key`, would improve structure slightly.

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 complex tool with nine action values, destructive behavior, no output schema, and 0% schema description coverage, the description covers many important semantics and safety constraints. It still leaves out the `key` parameter and the `revoke_key` action, which are material gaps for correct invocation. The account-view return shape is also unstated, though no output schema exists.

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 0%, so the description must carry parameter meaning. It explains most action values and the `confirm` requirement for destructive account actions, and it implies `webhook_url` through the webhook action. However, it never explains the `key` parameter and omits the `revoke_key` action, leaving meaningful gaps.

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 uses specific verbs and resources for account viewing, preference management, personalization clearing, account deletion, and webhook management, so the tool's purpose is clear. It is distinguishable from the property-focused siblings. However, it omits the `revoke_key` action and does not explicitly contrast itself with any sibling.

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 gives concrete prerequisites for sensitive actions: `clear_personalization` and `delete_account` need `confirm: true` and an explicit request, and webhooks are limited to paid plans. It does not name alternatives or when-not-to-use cases, but no sibling tool appears to cover account management, so the guidance is reasonably clear.

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