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 a genuine behavioral trait beyond that: platforms with no native equivalent 'say so instead of naming one,' which tells the agent how to interpret a missing name.

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 platform coverage are front-loaded in the first sentence, followed by two short clarifying sentences about the reverse lookup and the fallback. The long platform enumeration is dense but carries real information; no sentence is wasted.

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 takes on the burden of describing returns, and it does: component names per platform, pattern equivalents, and the explicit 'no native component' fallback. What is missing is guidance on how it relates to the sibling pattern/compare tools.

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%, so both parameters are already documented in the schema, giving a baseline of 3. The description restates that query can be a pattern id/name/description or a framework component name and that platform is an optional single-platform filter, adding little beyond the schema's own examples.

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 pins down a specific verb (returns/works backwards) and a concrete resource (component names per platform), and it enumerates the platforms covered, so an agent can tell this is a cross-platform naming lookup rather than a pattern browser. It never names a sibling tool (e.g. get_ui_pattern, compare_ui_patterns), so differentiation is inferred rather than stated.

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 dual direction of the query (pattern → names, or component name → pattern) implies two usage modes, and the optional platform filter is mentioned, but there is no explicit when-to-use/when-not and no routing to siblings like get_ui_pattern or compare_ui_patterns. Usage must be inferred from the query semantics.

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