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

Annotations already mark this as read-only; the description adds useful behavioral context by stating that the result contains page embeds and stable block ids intended for deep links. This goes beyond the annotations without contradicting them.

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 concise sentences: the first gives the selection trigger and the second gives the key output characteristic. No filler or repetition; the structure is well front-loaded.

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 single-parameter, read-only tool, the description gives the essential use case and return nature, but with no output schema and no parameter documentation it does not fully specify what `handle` must be or what the embeds structure looks like. An agent can make a reasonable guess, but not with full certainty.

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?

With 0% schema description coverage, the description is the only source for understanding `handle`, but it never actually defines what `handle` refers to or what format it should take. The resource phrasing implies an artist handle, but the mention of 'a specific published mix or set' leaves ambiguity about whether the same handle covers mixes/sets or whether they are addressed differently.

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 states a concrete resource — an artist's Dizko page or a specific published mix/set — and says the tool returns page embeds with stable block ids. It is clearly scoped and distinguishable from event-focused siblings, though it does not explicitly name an alternative or contrast with any sibling.

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 opens with an explicit 'Use this when a user wants...' trigger, which gives clear context for when to invoke it. It does not, however, state when not to use it or point to an alternative tool, so it falls short of full routing guidance.

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