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

Goes well past the annotations: destructiveHint=true already signals danger, but the description explains the concrete cascade — QUALIFIER steps pointing at the persona break and the referencing campaign's flow will fail to save — and that a shared persona breaks several flows. It also flags irreversibility and a plan requirement, which annotations cannot express.

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?

Front-loads the action, then stacks consequence, required pre-check, alternative tool, and prerequisite in that order. Every sentence carries distinct operational information — nothing is padding or restatement of the title.

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 one-parameter destructive tool with no output schema, the description covers everything an agent needs before calling: consequence of the write, verification step, confirmation requirement, alternative, and access prerequisite. No relevant gap remains.

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% and there is only one required string parameter, so the schema already does the work. The description's only added value is indirectly pointing at `persona_list` as the source of persona ids and `usageCount`, which is consistent with the schema's own description rather than new semantics.

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 and resource ("Delete a persona") in the first three words, and immediately contrasts with `persona_update` for the non-destructive alternative. An agent can distinguish it from `persona_get`/`persona_list`/`persona_update` without opening any 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 an explicit pre-flight procedure (check `usageCount` via `persona_list`, report affected campaigns, obtain explicit confirmation) and names the alternative tool `persona_update` with the condition that selects it. It also states a hard eligibility gate (Pro or Agency plan).

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