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

Annotations already establish readOnly/non-destructive, so the bar is lower; the description still adds real behavior: with no filters it enumerates everything by section with notes, and with filters it caps results at 8 at a time. No disclosure of image format, resolution, or failure modes, hence 4 rather than 5.

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?

Front-loaded with the core action, then the two behavioral modes, then the rationale. The closing sentence about text room and texture is somewhat motivational but does justify why seeing the image matters, so it earns most of its space.

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?

No output schema exists, so the description must convey returns — and it does (list of pictures by section with notes, or up to 8 shown images). Combined with full schema coverage this is nearly complete, though it says nothing about how images are delivered (URL vs. inline).

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%, so 3 is the baseline; the description goes beyond it by explaining the semantics of `section` (a section title like 'Imagery') and `names` (as the brief lists them) and by clarifying their mutual effect on output (list vs. show, max 8).

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 ('Look at the pictures in a brand kit') and enumerates what a kit contains (logos, product marks, footage stills, layout references, examples), which clearly separates it from data-returning siblings like napkin_brand_get or napkin_brand_examples.

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?

Explicitly frames the timing ('before you use them', 'Look before you build a design around a picture') and gives the rationale for doing so. It doesn't name a competing sibling tool to route against, so it falls short of a 5.

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