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

Annotations already mark this as destructive, and the description adds a meaningful boundary: it deletes the product screenshot but not Brand Memory. This gives useful behavioral context beyond the structured annotations, though it does not discuss irreversibility or side effects.

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 two short sentences with no filler. The primary action is front-loaded, and the second sentence earns its place by clarifying the deletion scope.

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 single-parameter destructive tool with an output schema and annotations, the description covers the essential behavior and scope well. Minor gap: it does not point to list_product_screens as a way to find the screen_id, but this is not a critical omission given the tool's simplicity.

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 has one required string, screen_id, with 0% description coverage. The description does not explain what screen_id refers to or how to obtain it, though the parameter name is reasonably self-explanatory from context.

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 uses a specific verb-resource pair, 'Remove a product screenshot from Brand DNA,' and explicitly distinguishes this from deleting Brand Memory. This clearly identifies what the tool does and separates it from nearby concepts.

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 implies this tool is for removing screenshots while preserving Brand Memory, but it does not explicitly state when to use it over update_product_screen or upload_product_screen. The usage context is clear enough, but no direct alternatives or when-not-to-use guidance is provided.

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