search-components-toolSearch Aura UI components by keyword (matches name, title and description). Returns matching components with their Blade tag and tier. Use this when you need a component for a purpose, e.g. "date", "table", "notification".
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keyword(s) to search for across component names and descriptions. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With empty annotations, the description carries the behavioral disclosure burden. It discloses that this is a read/search operation matching on name, title, and description fields. However, it doesn't describe behavior details like whether it's fuzzy matching, case sensitivity, ranking, or pagination of results—useful but not critical context.
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 a compact two-sentence format that front-loads the purpose, clarifies what's returned, and gives a usage example. Slightly verbose example list but overall efficient and zero waste.
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 single-parameter search tool with 100% schema coverage and clear sibling context, the description adequately covers purpose, return info, and usage triggers. It lacks detail on result ranking/ordering but that's unlikely to be essential for this tool type.
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%, and the description reinforces that the query matches across 'name, title and description.' The description adds the scope of the match (which fields are searched) beyond the bare schema definition, providing moderate added value.
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 purpose is very clear: 'Search Aura UI components by keyword (matches name, title and description)' uses a specific verb+resource with explicit search scope. It also states what's returned ('matching components with their Blade tag and tier'), distinguishing it effectively from siblings like list-components-tool.
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 explicitly tells the agent when to use it: 'Use this when you need a component for a purpose, e.g. date, table, notification.' It provides good usage context, though it doesn't explicitly mention when NOT to use it or name alternatives like list-components-tool vs get-component-tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: list/search for discovery, get for detailed info, add for installation, and filament-theme for Filament panel theming. There is no overlap between the tools, and even search vs list are clearly different (keyword-based vs full list).
Four of the five tools follow a clear verb-noun pattern (add-component, get-component, list-components, search-components). The exception is 'filament-theme-tool', which uses a noun prefix rather than a verb, creating a minor inconsistency in the naming scheme.
With only 5 tools, the set is well-scoped and focused on the core tasks of discovering, inspecting, and installing Aura UI components, plus a separate theming tool. It is neither too sparse nor overloaded for its purpose.
The tools cover the complete workflow an agent needs: discovering components (list/search), getting full details (get), and installing them (add). The additional filament-theme tool addresses a related but distinct need. No essential operation is missing for the stated domain.