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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's 'Read-only, no site needed' is confirmatory rather than new. It does add non-annotation behavior: an omitted intent returns the full pattern list, and v4 recipes return an `atomic` spec rather than a plain section spec.

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?

Purpose and downstream consumer are front-loaded in the first clause, and the recipe list is dense but scannable. The trailing parenthetical with an ellipsis and the abbreviation-heavy 'Editor V4 atomic recipes too' fragment add slight clutter.

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 return-value burden and does so adequately by stating it yields a paste-ready section spec and, for v4 recipes, an `atomic` spec. Read-only and no-site-required are stated; only the exact return shape and whether recipes are paginated remain unspecified.

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 100% and there is only one optional parameter, so the schema already documents `intent` fully. The description adds example values ('hero with curved bottom', 'stats band') and the omit-to-list-all fallback, which is useful but marginal over the schema's own description.

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 concrete verb+resource ('Design suggestions: intent → a paste-ready section spec') and enumerates the actual recipe vocabulary (hero with overlay, wave divider, stats band, v4-tabs, v4-hero). An agent can distinguish this from the wp_* mutation siblings it feeds, since it explicitly names wp_create_page / wp_replace_section as downstream consumers.

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 an explicit usage rule: 'Call with no intent to list all patterns', and states 'Read-only, no site needed', which tells the agent it can invoke this before a site context exists. It does not, however, differentiate itself from nearby design-oriented siblings such as design_recommend, design_search, or assist_design_lint.

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