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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds useful structural context: each section links back to its page via parent_slug and to the product design system, plus a recommended follow-up call. It does not describe return shape, section count limits, or pagination.

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 sentences, no filler, with the resource and its examples front-loaded ahead of the follow-up guidance. Slightly dense with parenthetical examples but every clause carries information.

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 simple single-param read tool with no output schema, the description covers what is returned (distinct page sections), the cross-references in each result, and the related design-system call. Only the input slug's meaning and any result-size behavior are unaddressed.

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 required parameter 'slug' is never explained in the description. The text mentions parent_slug only as an output field, not as the input identifier. The meaning of the input is inferable from 'sections of a page' but not stated, leaving the one required param undocumented.

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 (List) and resource (distinct sections of a page) and enumerates concrete examples (hero, pricing cards, testimonial/feedback, footer). It implicitly contrasts with the singular get_section and the comparative compare_sections by scoping to a page's full section set, though it never names those siblings explicitly.

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 a motive ('so you can emulate a specific part') and a follow-up action (call get_design_system(site)), which implies usage context. However, it offers no explicit when-to-use vs when-not, and no comparison to get_section or compare_sections, so the routing decision is left partly to inference.

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