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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds a real behavioral constraint beyond them: only *published* dossiers are returned, plus the shape of each record (name, slug, subtitle, editions, tier, updated date). It omits pagination or ordering behavior for what could be a large list.

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 short sentences, front-loaded with the scope ("every published") and followed by the use case. No filler or repetition of the title.

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, enumerating the returned fields is what makes this complete, and the annotations carry the safety profile. The only gap is that a "list every" tool gives no hint about pagination, result size, or ordering.

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 takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The listed return fields are a bonus, not a parameter explanation.

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 (List) plus resource (published AB[500] artist dossiers) and enumerates the returned fields, so an agent immediately knows this is a bulk enumeration rather than a single-record fetch. It is cleanly separable from the sibling get_dossier, which returns one dossier.

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?

"Use it to see which artists have a published biography" gives a clear triggering context, so the agent knows when to reach for it. It stops short of naming alternatives or exclusions (e.g. use get_dossier for full detail), so it does not reach the 5 threshold.

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