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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, lowering the transparency burden. The description adds value by disclosing the return content (do's, don'ts, evidence, and checklists), which is important since there is no output schema to carry that information. No contradiction exists between the description and annotations.

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 description is two sentences with zero wasted words. The first sentence front-loads the core purpose and the second efficiently enumerates supported pattern types. Every clause earns its place.

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 retrieval tool with 3 well-documented parameters, robust annotations, and no output schema, the description is reasonably complete: it states the return format (do's, don'ts, evidence, checklists) and the full domain of pattern types. Slightly more detail on filtering behavior or output structure would push it to a 5, but it is adequate as-is.

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%, with all three parameters (type, goal, platform) already documented and two having enums, so the baseline of 3 applies. The description adds no parameter-specific meaning beyond what the schema provides, such as example values or format details.

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 uses a specific verb+resource construction ('Get proven UI/UX patterns for a specific design type') and enumerates 13 concrete pattern types (signup flows, pricing pages, dashboards, etc.), making the tool's scope unmistakable. This enumeration implicitly differentiates it from sibling tools like get_content_pattern, get_service_pattern, and get_checklist by specifying exactly which UI/UX pattern domains it covers.

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 establishes clear usage context by defining the tool as a pattern reference for specific design types and stating what it returns (do's, don'ts, evidence, checklists). However, it does not explicitly name alternatives or provide when-not-to-use guidance relative to siblings such as get_checklist or get_design_system, stopping short of the top score.

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