delete_pixel

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

No annotations exist, so the description carries the full burden for a destructive mutation. It says nothing about permanence, whether historical tracking/metric data tied to the pixel is preserved or lost, required scopes, or what happens when the pixelId does not exist — all material for a delete operation.

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?

Four words, front-loaded and waste-free, but the brevity crosses into under-specification for a destructive tool. Conciseness is achieved by omission rather than by tight writing.

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?

With no annotations and no output schema, the definition provides no safety, permissions, or failure-mode context for a delete in a family of pixel tools. An agent can guess the effect but not the consequences.

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% for the single required parameter, and the description says nothing about pixelId — not how to obtain one (e.g. via list_pixels), nor that it is a UUID. The schema's type/format hints are the only source of parameter meaning.

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 tracking pixel'), which is unambiguous against siblings like create_pixel, update_pixel or delete_website. It does not differentiate itself from related cleanup actions (e.g. update_pixel to disable, or deleting a link), but the name-plus-description pair leaves no real ambiguity about the operation.

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?

There is no guidance on when to delete versus update/disable a pixel, no prerequisites, and no warning about irreversibility. The agent must infer everything from the tool name alone.

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