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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the marginal bar is low. The description still adds genuinely useful behavior: the return is Markdown and its contents are enumerated, which matters because there is no output schema. It stops short of noting document size or that the whole skill must be retained in context, which would be the last piece of helpful context.

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?

Front-loaded with the deliverable and its format, with the directive sentence last where it belongs. The parenthetical rule list is long but each item is load-bearing content, not filler; the single sentence is dense and slightly run-on, which is the only cost.

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 zero-parameter, no-output-schema tool, the description carries the full burden and largely meets it by naming the return format and summarizing the payload. It is complete enough to call correctly, though a note on document length or how to apply the skill across a session would close the remaining gap.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter text is present, but none is needed.

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 and resource ('Get the Eased design skill as Markdown') and then enumerates what the document contains — install/compose guidance, tokens, and the checkable rules. An agent can distinguish this from list_components, search_components, get_component and get_install_command without opening any schema.

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?

Gives explicit sequencing ('Call it first, before you build or change UI with Eased') plus an ongoing obligation ('follow it while you work'). This is a rare case of a tool that states both the trigger condition and the alternatives by implication — the sibling tools are for looking up individual pieces, this one is the prerequisite.

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