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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds one useful operational fact: an unfiltered call returns the complete catalog. It says nothing about pagination, ordering, or result size limits, which matters for a catalog listing.

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 short sentences with the domain context front-loaded, followed by filter capabilities and the no-filter behavior. Nothing is repeated or padded.

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 should sketch what a returned item looks like (identifier, name, tier, category) so an agent can chain into get_component or get_install_command. It mentions only 'every item is returned', leaving the result shape and ordering unspecified.

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%, including enum descriptions for kind and tier, so the schema already explains every parameter. The description only restates the filter names and their optionality, adding no new semantics such as combining filters or match behavior.

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 ('List Facade components and blocks') and immediately clarifies what those things are ('animated React + Tailwind sections for local business, real estate and agency sites'). This distinguishes it from the sibling get_component, which retrieves a single item by name.

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 states that all filters are optional and that no filter returns every item, which is useful context. However, it never names an alternative (e.g., get_component for a single item, suggest_page for recommendations) or states when filtering is preferred over listing everything.

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