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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real value by disclosing the response shape (subtitle, markdown prose, identity, works, images, bibliography with source URLs) and the CC0 licensing of the prose, which the annotations do not 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?

Two sentences, front-loaded with the action and key requirement, then a tight enumeration of returned content. No filler, no repetition of structured fields, and the licensing note is short and relevant.

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?

With no output schema, the description carries the burden of describing the return payload and does so thoroughly. It omits edge cases such as behavior for an unknown slug or payload size limits, but for a single-entity read-only fetch it is essentially complete.

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 the single 'slug' parameter is fully documented in the schema, including an example and its origin (list_dossiers/search_artists). The description only restates 'by slug' and adds no format or validation detail beyond the structured field, so the 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 ('Get one artist's full structured biography by slug') and enumerates the exact contents returned. The singular 'one artist's ... by slug' clearly separates it from list_dossiers and search_artists without needing to name them.

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: 'by slug' signals the key requirement and 'one artist' implies fetching a single record after a listing. However, no sibling is named and there is no explicit when-to-use/when-not guidance, leaving the agent to infer the lookup-after-search flow.

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