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

The annotations already declare this as a read-only, idempotent, non-destructive fetch, so the description's job is added context — and it delivers: it discloses that reviews return written text plus author rather than just a score, and it explains the empty-list ambiguity (no items vs. hidden items). It omits ordering/pagination behavior despite a limit parameter existing.

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?

Four sentences, front-loaded with the key clarification about review text, and each subsequent clause covers one kind. The opening "in full" is slightly loose given a default limit of 25 and could be tightened.

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 returns; it covers reviews well but only vaguely characterizes the shapes of mixes, posts, and live-events. The claim of "in full" sits awkwardly against a limit parameter with a default of 25 and no pagination or total-count discussion.

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%, so the 3 baseline applies, but the description goes further by explaining what each kind value actually yields (sets and where to hear them, upcoming gigs, recent activity, full review text). It adds no meaning for limit or id_or_slug beyond the schema.

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 names the resource (a DJ's published content) and enumerates the four collections it can return — mixes, posts, live-events, reviews — so an agent can tell what it fetches. It does not distinguish itself from near-siblings like get_mix, get_post, or get_review_summary, which is the main reason 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?

"Call it whenever someone asks what clients said" is a concrete, actionable trigger, and each kind is given a usage gloss (e.g. live-events = what they are playing next). There is no when-not guidance and no explicit routing to list_mixes, get_post, or get_review_summary for single-item or summary lookups.

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