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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety bar is lower; the description nonetheless adds real context beyond them: the stored image is deleted along with the record (a cascade effect), the action is irreversible, and owner-level permissions are required. It stops short of stating error behavior for missing/in-use sprites.

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 short sentences, front-loaded with what is deleted, followed by consequences, irreversibility, and authorization. No filler or restatement of the tool name.

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 one-parameter destructive tool with no output schema and full annotation coverage, the description covers effect, side effect, irreversibility, and permissions. Only missing a note on failure modes (invalid id, permissions error) to be fully complete.

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?

Single parameter with 100% schema description coverage, including where to obtain the uuid (list_sprites). The description adds nothing about the parameter, so the schema is doing all the work — baseline 3 applies.

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 custom sprite icon') plus what is removed ('its stored image'), which distinguishes it from list_sprites and from style/dataset deletion siblings. An agent can identify it without opening the schema.

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?

Provides a clear precondition ('Workspace owner only') and the practical consequence of deletion ('a style still referencing it will show no icon there'), which tells the agent when the call is appropriate. It does not name an alternative (e.g., update_style to swap the icon) or say what happens for a nonexistent id.

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