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

Annotations already establish read-only and closed-world behavior. The description adds meaningful behavioral context: common synonyms are understood, results are ranked as 'best matches,' and results include install commands. It does not cover ranking details or result limits, but it is strong for an annotated read-only search tool.

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 three compact sentences with no wasted wording. The core search scope is front-loaded, followed by useful examples and a concise return-value note.

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 read-only search tool with no output schema, the description gives enough to call it correctly: what is searched, example queries, synonym behavior, and that install commands are returned. Minor gaps remain around result limits, ranking, and explicit routing versus sibling list/get 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 coverage is 67%, and the description adds useful query semantics through examples and synonym handling beyond the schema's bare 'What to find.' However, it does not explain the limit parameter or add much beyond the schema's detailed type enum descriptions.

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 clearly states a specific verb and resource: search components, charts, blocks, templates, patterns, and hooks by need. It does not explicitly name or contrast with sibling tools such as list_items, so it is clear but lacks explicit sibling differentiation.

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?

Usage is implied through phrases like 'by what you need' and examples such as 'date picker' and 'confirm before delete', suggesting semantic/keyword search. However, it does not explicitly say when to use this tool versus list_items or get_item, nor does it state exclusions.

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