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

Annotations already declare readOnly=false, idempotent=false, destructive=false. The description adds value beyond them: no replay receipt on creation, the list is the source of truth after an ambiguous result, and no generation or credit charge occurs. That idempotency/retry context is exactly what the annotations can't convey.

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?

Four short sentences, purpose front-loaded, no filler. The telegraphic phrasing ("No generation or charge") is efficient, though a couple of clauses about replay receipts read slightly clipped rather than polished.

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?

For a 10-param creation tool with annotations and an output schema, the description covers the essentials: required input, where photos live, catalogue selection, retry behavior, and cost. Return values need not be detailed since an output schema exists. Nothing critical is missing, though a pointer to studio_artists_list by name would tighten the post-failure path.

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 all ten parameters including the identityKind enum are already documented in the schema. The description restates required name and adds that catalogueArtistId is optional/account-dependent, but the schema already carries that note, so the added meaning is marginal. Baseline 3 applies.

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 ("Creates an artist") and even names the return payload (profile and revision), which is more than the title alone. It routes photo work to dedicated tools, implicitly separating it from studio_artist_photo/reference_add, but never explicitly contrasts with studio_artist_update, so the sibling boundary for the mutation case stays implicit.

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?

Gives concrete usage conditions: name is required, photos go through other tools, and catalogueArtistId is only needed to select a catalogue on multi-catalogue accounts. It also tells the agent what to do after an uncertain response (read the artist list), which is real operational guidance. It stops short of explicit when-not-to-use-this-instead-of-update guidance.

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