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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond them by disclosing what comes back (page embeds with stable block ids suitable for deep links), which matters because there is no output schema.

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 tight sentences: the trigger condition is front-loaded and the return behavior follows. No filler, no repetition of the title or annotations.

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?

For a one-parameter read-only tool with annotations covering the safety profile and no output schema, the description covers purpose and return shape adequately. The unresolved meaning of `handle` (artist vs. mix) is the main completeness gap an agent would hit before calling it.

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 description coverage is 0% and the single parameter `handle` is never explained in the description. Worse, the description's phrasing (artist page vs. a specific mix or set) creates ambiguity about whether handle identifies an artist or a mix, so it does not compensate for the schema gap.

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 a specific resource (an artist's Dizko page, a published mix/set) and implies a read of page embeds, so the agent can tell what it returns. It does not explicitly distinguish itself from the sibling get_artist tool, which is the most likely confusion point, so it falls 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?

"Use this when a user wants an artist's Dizko page or a specific published mix or set" gives a trigger condition, but it restates the purpose rather than offering when-not-to-use guidance or naming alternatives such as get_artist. The mention of a "specific published mix or set" is also not reconcilable with the single required handle parameter, leaving usage partly implied.

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