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

Annotations already declare destructiveHint/idempotentHint, but the description adds material context beyond them: the permission requirement, that the updated identity pack is returned, that future likeness generation is affected, and that older pinned projects retain existing rules. That downstream-impact disclosure is exactly the kind of behavior an agent cannot get from the annotation block.

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 with the destructive action front-loaded and consequences following. The only filler is the vague phrase "using the app service," which contributes nothing an agent can act on.

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 destructive mutation with rich annotations, a fully documented schema and an output schema, the description covers permissions, side effects, return value and scope limits. The remaining gap is the absence of alternative routing, which is minor given the annotation coverage.

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% and both parameters cross-reference their source tools (studio_artists_list/studio_artist_read, studio_artist_dna_read), so the schema carries the semantic load. The description adds nothing about parameter form or provenance, making the baseline 3 appropriate.

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?

Uses a concrete verb ("Remove") plus a precise resource ("one identity reference photo"), which separates it from studio_artist_reference_add and the generic studio_reference_delete. It does not name those siblings explicitly, so an agent still has to infer the boundary, but the scope is unambiguous.

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 states two real prerequisites (artist-level permission, the customer selecting that exact photo), which is genuine usage context. However, it never says when to prefer this over studio_reference_delete or studio_artist_reference_add, so the routing decision is left to inference.

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