delete_pixel

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete a pixel' and does not reveal any consequences, irreversibility, permissions, or side effects. The description adds no behavioral context beyond the name itself.

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 extremely brief and front-loaded, with no wasted words, but it is under-specified. While concise, the three-word phrase lacks sufficient detail to be considered appropriately sized for a tool that might have nuances (e.g., distinguishing pixel types). It is not egregious but minimal.

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?

The tool is simple (one parameter, no output schema), but the description is incomplete for contextual use. It does not mention any differences from similar delete tools, nor any effects of deletion. Given the sibling 'delete_custom_pixel', the description fails to provide enough context for correct selection.

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?

The input schema covers 100% of the parameter ('id') with a description. The tool description itself adds nothing beyond the schema, so the baseline score of 3 applies. No additional parameter meaning is conveyed.

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 'Delete a pixel' clearly states the action (delete) and resource (pixel). It is specific but does not distinguish between standard pixels and custom pixels, especially given the sibling tool 'delete_custom_pixel'. Thus it is clear but lacks sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives like 'delete_custom_pixel' or other delete tools. It does not mention any prerequisites or context, leaving the agent without usage direction.

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