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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuine value beyond that: results are grouped by suite, defaults to cheap compact triage, and 'full' inlines snippets and confidence flags. It does not disclose result volume, ordering, or what happens on zero matches.

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?

Three tightly packed sentences, front-loaded with the core purpose, then when-to-use, then the verbosity default that matters most for cost. No filler.

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 does the work of explaining the return shape (patterns grouped by suite; snippets and confidence flags in full mode) and the intended workflow. Minor gap: limit semantics and the behavior at low/zero relevance 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 coverage is 0%, so the description carries the full burden. It explains verbosity well (compact = cheap triage, full = inline snippets and confidence flags), but says nothing about the limit parameter's role or default, and only implicitly characterizes task via the example.

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 a specific verb and resource ('return the most relevant patterns grouped by suite') from a natural-language task, and it contrasts its role with get_requirement as the follow-up tool. It does not distinguish itself from the similarly-named sibling search_patterns, so an agent can't tell those two apart from the text alone.

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?

Explicitly positions itself as 'a starting point for any cross-cutting design question' with a clear follow-up path via get_requirement on specific pattern_ids. It stops short of naming search_patterns or stating when this tool should NOT be used instead.

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