List product photos

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral traits: it is free, returns URL and label, surfaces photos locked in other creations, and switches the active brand when brandId is provided. This goes beyond the annotations.

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 moderately concise, with the main action front-loaded. Every sentence provides useful information, though the parenthetical about other creations adds some length. Could be slightly tighter but overall well-structured.

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?

Given that the tool has an output schema (not shown but referenced), the description explains what is returned (url and label) and the behavior of including photos from other creations. With zero required parameters and good annotations, this is complete for a simple read-only list tool.

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 baseline is 3. The description adds meaning: omitting brandId uses the active brand, and passing it switches the active brand. This adds value beyond the schema's description.

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 states the tool lists product photos already saved in the workspace, specifying the resource (product photos) and the action (list). It doesn't explicitly distinguish from other list tools like list_brands, but it mentions a related sibling (set_product_image), providing some differentiation.

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 description tells when to use the tool: 'Call it before set_product_image to see the existing photos you can reuse.' It also explains the effect of passing brandId (switching active brand). However, it does not explicitly state when not to use it or compare to other listing tools.

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