Delete user data (pixel)

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely useful context by disclosing the required scope and the business-admin role needed to invoke it. It stops short of describing the async job behavior or return/status handling.

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?

A single front-loaded sentence naming the action, resource, and the gating requirement in a parenthetical. No wasted words.

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 an open-world, mutating job-creation tool with nested parameters and no output schema, the description gives prerequisites but no sense of rate limits, job lifecycle, or how the resulting job is retrieved. Adequate but leaves meaningful gaps for a compliance-sensitive data deletion operation.

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 the load; it conceptually maps 'person's data' to the data/identifiers payload and 'a pixel' to pixel_id. However it omits the meaningful constraints in the schema (identifier type enum, SHA-256 hashing option, maxItems of 200), so it only partially compensates.

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: requesting deletion of a person's data collected by a pixel. This distinguishes it from the sibling reddit_ads_create_data_deletion_job by scoping to pixel-collected data, though the sibling relationship is left implicit rather than named.

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?

The prerequisite (adsdatadeletion scope and business admin) is a useful precondition, but there is no guidance on when to choose this tool over the generic reddit_ads_create_data_deletion_job sibling or the get_data_deletion_job follow-up. Usage is only implied by the pixel-specific framing.

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