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

Annotations already establish this as a safe, idempotent read operation, but the description adds meaningful context: the four status values, that 'rendering' means wait about a minute, that image_url appears only once drawn, and what 'kept' and ownership mean. It does not cover error cases such as an unknown lookbook_id, but the added behavioral value is substantial.

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 definition is compact with no filler, but it is a single run-on sentence with awkward phrasing ('as they are drawn status is proposed', 'price: per picture, to draw the rest') that forces re-reading. The return-shape details are front-loaded, but the purpose statement itself is not clearly leading.

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?

There is no output schema, so the description carries the burden of explaining returns. It covers the piece-level fields and status transitions reasonably well, but the overall response shape and the pricing semantics remain vague, and error behavior is unaddressed.

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 coverage is 100% and the single lookbook_id parameter is fully documented with a pattern, so the baseline of 3 applies. The description adds no further meaning about the identifier or format beyond what the schema already provides.

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 identifies the resource as a lookbook and describes its contents and status lifecycle, which is specific enough to distinguish it from generic look tools. However, it doesn't explicitly contrast with siblings like get_look or list_looks, so an agent must infer that this is the music-video lookbook variant.

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?

Usage is implied rather than stated: retrieving a lookbook and polling when status is 'rendering' ('check back in about a minute') gives a clear operational hint. There is no explicit guidance on when to use this versus get_look, list_looks, or update_music_video_lookbook, leaving alternatives to inference.

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