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

The annotations already mark it as readOnly, idempotent, and non-destructive, so the description doesn't need to repeat that. It adds the 'published' qualifier and lists return fields, which is some extra context. However, it doesn't mention pagination, limits, or any potential side effects beyond what annotations cover, so it's adequate but not rich.

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 description is a single, concise sentence that states the action, the resource, the filter (published), and the returned fields. It has no redundant words and is front-loaded with the primary purpose.

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?

Given there is no output schema, the description compensates by listing the specific fields returned (name, slug, subtitle, editions, tier, updated date). It also clarifies the 'published' filter, which is useful. It doesn't mention pagination or limits, but for a simple list tool, the provided details are sufficient to understand what the tool returns.

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?

The tool has zero parameters, so the schema covers 100% of them. With a 100% coverage, the baseline is 3. The description adds no parameter semantics because there are none, which is 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?

The description clearly states the tool lists every published AB[500] artist dossier and enumerates the fields returned. It also distinguishes itself from siblings by indicating it is the starting point for discovering which artists have a biography available, contrasting with get_dossier and other retrieval actions.

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 implies when to use it ('Start here') and hints that it serves discovery, but it does not explicitly state when to prefer this over sibling tools like get_dossier or search_artists. The guidance is present but not fully explicit.

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