Search labsUI

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds matching semantics ('All words must match, best match first') plus a return shape ('one line per hit: name, kind and summary'). It stops short of noting truncation behavior or how to widen a too-narrow match, but the added context is solid.

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, front-loaded with purpose, then matching rules, then return shape and the next-step routing. No filler or restatement of the title.

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 carries the return-format burden and does so ('one line per hit: name, kind and summary'). Combined with annotations and full schema coverage, an agent has everything needed to call this and act on results.

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 the baseline is 3; the description earns extra by explaining matching behavior for query (all words must match, best-first ordering, empty lists everything) and by noting exports are searchable targets. It adds no detail on kind or limit beyond the enum and bounds already in the schema.

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 and resource ('Find labsUI components, blocks, hooks and helpers') and enumerates the three matchable facets: name, export, and intent. This is clearly distinguishable from siblings like view, add, or update without opening any schema.

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 says 'Start here when you don't know an item's name, then call view on the hits,' naming the alternative and the condition that selects it. Also covers the degenerate case: 'no query lists everything.'

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