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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: that the operation is free (no credit cost), that pagination caps at 50 per page, and that fictional characters need no likeness consent while real-person artists retain the consent flow.

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 core purpose and returned fields are front-loaded, followed by short behavioral notes. Every sentence carries information (cost, pagination, consent semantics), though the consent-flow sentence is slightly tangential to selection and invocation.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description supplies the remaining essentials an agent needs (free, paginated, 50-per-page, identity semantics), leaving only explicit sibling routing unaddressed.

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 description coverage is 100%, so limit, query and cursor are already documented in the schema. The description only restates the 50-per-page cap on limit and mentions pagination, adding no syntax or format detail beyond what the schema provides, so the baseline of 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 ('Lists the customer's artists alphabetically') and enumerates the attributes returned (IDs, names, identity kind, photo count, face-check status, video-model eligibility). This clearly separates it from the singular studio_artist_read, but it never explicitly names a sibling alternative, so it stops short of a 5.

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 notes that listing is 'Free, read-only' with pagination up to 50 per page, which implies the browse-all use case, but it gives no explicit when-to-use or when-not guidance and never routes the agent to alternatives like studio_artist_read or studio_artist_actor_read for single-record lookups.

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