search_prefab_components

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

With no annotations, the description explains query matching (OR-matched), automatic detail modes based on result count, and the detail parameter override. It does not mention read-only nature explicitly but implies it. The behavior is well-covered.

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 front-loaded with purpose and usage, followed by parameter details. It is clear and well-structured, though the parameter descriptions are somewhat repetitive of the schema. Still, no unnecessary information.

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?

Given the tool's complexity (4 parameters, output schema provided), the description covers purpose, usage context, parameter behavior, and output modes thoroughly. The output schema exists, so return format details are not needed. The description is complete for an API search tool.

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 75%, and the description adds meaningful context for query, detail, and limit beyond the schema. The `components` parameter lacks description in both schema and description, but the description compensates for the other three with usage details like OR-matching and automatic mode.

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 it searches the Prefab component library to look up API details, distinguishing it from sibling tools which are unrelated (GitHub operations). The verb 'search' and resource 'component library' are specific and precise.

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 explicitly advises using this tool before writing component code to find argument names and values, and contrasts it with a separate skill for patterns and layout. However, it does not name the alternative tool or explicitly state when not to use it.

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