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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful content-scope context about what each mode returns, but says nothing about response size, format, or whether guides are static vs. site-specific.

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?

The default no-topic behavior is correctly front-loaded, but the long enumeration of eighteen self-descriptive topic names (domains, blocks, editing, theme, pages, site) largely restates the enum without adding meaning, inflating the sentence considerably.

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 one optional enum parameter, full schema coverage, and annotations covering the safety profile, the description provides everything needed to invoke the tool correctly. The absence of an output schema means return values could have been described, but the topic enumeration implicitly covers that.

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% and the enum already lists all 26 values, so the baseline is 3. The description earns more by explaining what the liquid topics actually cover (files, tags, filters, runtime data-* attributes, forms, dates) and by decomposing the liquid-<part> suffix pattern, which the enum names alone do not convey.

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 the resource clearly as a 'styling and authoring reference' and enumerates what content is returned for each topic, so an agent knows this is a documentation lookup rather than a mutation. It does not name a sibling it is distinct from (e.g. set_theme, suggest_palettes), but the purpose is unambiguous on its own.

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?

It explicitly covers the two invocation modes: no `topic` returns the core reference (palette variables, styleGuide tokens, spatial scale, class rules, section skeleton), and passing `topic` returns a focused guide. There is no guidance on when to prefer this over related tools like set_theme or suggest_palettes, which keeps it below a 5.

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