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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds a genuinely useful behavioral caveat — that career details are 'as provided by the artist, not independently verified' — which is provenance context the annotations cannot convey. It stops short of describing pagination or failure behavior for an unknown slug.

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?

A single densely packed sentence front-loads the resource type and then lists return contents, with a compact 'Read-only.' tag at the end. No filler, though the field list is long and could be trimmed where the schema/output already imply structure.

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?

There is no output schema, so the description correctly carries the burden of enumerating return fields, and it does so thoroughly, including works and their availability. The only gaps are error behavior for invalid slugs and pagination of works, which are minor for a single-entity read.

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 0%, so the schema documents only type/pattern/length for artist_slug with no prose. The description compensates partially by naming 'slug' as the identifier, clarifying the parameter's role, but gives no format guidance (lowercase, max 40 chars) beyond what the schema's pattern supplies.

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+resource ('Profile of one artist by slug') and then enumerates exactly what is returned — names, tagline, story, career, portrait, seal, certificate, works with availability. No sibling tool covers artists, so there is no ambiguity to resolve, and an agent knows precisely what this fetches.

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?

Usage is implied rather than stated: you call it when you have an artist slug and need the full profile. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative (e.g. search_products vs this). Adequate but leaves the agent to infer the trigger condition.

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