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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the description is not responsible for safety disclosure. It adds useful context by explaining what each returned URL represents (cropped 1536px image vs 320px thumbnail vs source rectangle) and how the kit relates to briefs. Pagination or ordering behavior is not mentioned.

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 informative but runs five dense sentences with nested parentheticals. The first sentence defines the domain concept rather than front-loading the listing action, and some phrasing (e.g. repeatedly explaining outfits vs places/props ownership) could be tightened. It earns most of its content but is verbose for a two-parameter list tool.

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 returned fields, and it does so well: name, @handle, url, thumbnail_url, source_url, width and height are all covered. The relationship to music video briefs is also explained. It lacks any statement about result ordering or pagination, which keeps it from a 5.

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 schema already documents both parameters at 100% coverage, so baseline is 3. The description adds real meaning for artist_id by spelling out the exact scope difference (workspace pieces + this artist's outfits vs all artists' outfits), which is more precise than the schema's terse 'Only the workspace's pieces and this artist's outfits'. The kind parameter gets only implied domain explanation.

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 clearly defines what is returned (outfits, places, props that make up the kit) and how those pieces relate to a music video brief. The verb 'list' comes from the title rather than the description, and no sibling tool (e.g. get_kit_piece, list_looks) is explicitly contrasted, so it falls short of a 5.

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?

It gives explicit conditional guidance: with artist_id you get the workspace's places and props plus that artist's outfits; without it you also get every artist's outfits. That covers the main decision an agent faces. It does not name when to use get_kit_piece instead or any other alternative, which keeps it from a 5.

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