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

Annotations mark destructiveHint=true but provide no detail. The description adds substantial context beyond them: Reddit has no hard delete for entities that ran, ARCHIVED is permanent and irreversible, the call returns a preview with a plan_id, and execution requires a separate double-confirmation step. That is exactly the behavioral disclosure a mutation tool needs.

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 and its irreversibility, then the alternative, then the preview/confirmation mechanics, closing with a doc link. Every sentence carries distinct information with no redundancy.

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?

Covers irreversibility, the archive-instead-of-delete caveat, the alternative tool, and the two-step confirmation flow. With an output schema present, the preview/plan_id return contract need not be restated, so nothing an agent needs to invoke it correctly 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 entity_id, entity_type and ad_account_id are already fully documented in the schema. The description adds only the enumeration of entity types, which the schema also provides, so it does not meaningfully extend parameter meaning beyond the baseline.

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 (Draft archiving/removal) applied to a named resource family (Reddit campaign, ad group or ad). It also makes clear this is a preview rather than an immediate mutation, which distinguishes it sharply from pause_reddit_entity and the update_reddit_* siblings.

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?

Explicitly names the reversible alternative (pause_reddit_entity) and the condition that should route the agent there: 'when the entity does not need to be gone.' It also states the confirmation workflow (plan_id, double confirmation, confirm_and_apply), so an agent knows the full call path.

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