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

Annotations already declare destructive/idempotent/non-readonly, but the description goes further: it discloses the cascade (pictures are deleted too), the non-refund of already-drawn pictures, and the two concrete 409 conditions. That is exactly the extra context annotations cannot express.

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?

Dense and front-loaded, but the phrasing is garbled and missing punctuation ("with its pictures Only a lookbook no shot list or video was made from"), which forces re-parsing. The parenthetical error codes are efficient, but the second sentence duplicates the first sentence's precondition.

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 destructive, single-parameter delete with no output schema, the description covers preconditions, cascade behavior, and refund semantics, which is nearly everything needed. It could briefly state what a successful call returns or whether the id remains queryable, but nothing essential to a correct call is missing.

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?

There is a single required parameter with 100% schema description coverage including a format pattern, so the schema carries all the meaning. The description adds nothing about lookbook_id beyond what the schema states; 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 concrete verb (deletes), resource (lookbook), and scope (only a lookbook nothing was made from), and explicitly notes what it also removes (its pictures). This separates it from sibling delete_music_video_look / delete_music_video_plan / delete_look without the agent having to open another 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?

The two 409 preconditions (a shot list or video exists; pictures are currently being drawn) effectively tell the agent when not to call it, and implicitly route a blocked case elsewhere. It does not name the alternative tool to use when a 409 would occur, so it falls short of a full routing instruction.

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