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

Annotations already establish read-only, idempotent, closed-world behavior, so the safety profile is covered. The description earns credit for disclosing result structure that annotations cannot convey: results are organized by group, and only the single-group mode includes descriptions — important because there is no output schema.

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?

A single front-loaded sentence with the primary mode first and the alternate mode second; no filler. The parenthetical group examples are slightly loose with the trailing ellipsis but still informative rather than wasteful.

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 two-optional-parameter, read-only listing tool with no output schema, the definition covers what matters: grouping of results and the difference in detail between the two modes. The only gap is that 'tier' filtering behavior is left entirely to the schema.

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 100%, so both 'tier' and 'group' are already documented at a high baseline. The description reinforces that omitting 'group' yields the overview and that including it yields descriptions, but adds no format, casing, or tier-interaction detail beyond what the schema provides.

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 describes the two result shapes (all items grouped, or one group's items with descriptions), with concrete group examples like 'Chat' and 'App shell'. It never literally says 'components' (only 'items'), but the title supplies that, and the grouping concept separates it from get_component_docs and search_docs well enough to act on.

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?

It implies two modes — an overview versus a single-group listing with descriptions — which is useful mode guidance. However, it never names alternatives like search_docs or get_component_docs, nor states when grouping is preferable to searching, so the agent must infer routing from sibling names alone.

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