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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the cap of up to 6 photos and their role as identity references versus cover art — but says nothing about return format or ordering.

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?

Two short sentences with the resource front-loaded, so it is not bloated. However, the second sentence is largely conceptual framing about how photos relate to Looks, Canvases and cover art, which does not help an agent invoke the tool correctly and does not earn its place as strongly as operational guidance would.

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?

This is a simple read-only, single-parameter list tool with no output schema, so the description need not explain return values. Still, it omits the one thing an agent would want for a list endpoint — what a photo entry looks like (id, URL, dimensions) — beyond the 'up to 6' count.

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 parameter (artist_id) with 100% schema description coverage, so the schema already carries the parameter semantics and the baseline is 3. The description adds no format, id-shape, or sourcing detail beyond what the schema 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 (an artist's photos, described as identity references) but uses a bare noun phrase with no verb, so it never actually states that it lists/retrieves them. It does implicitly separate these photos from cover art, which helps a little against siblings like set_artist_picture, but does not name any sibling or clarify the operation.

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?

There is no when-to-use guidance at all: nothing tells the agent when to call list_artist_photos versus add_artist_photos, delete_artist_photo, or get_artist. The framing sentence implies the photos matter for Looks/Canvases, but no actionable selection criteria are given.

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