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

With no annotations, the description carries the full behavioral burden and does substantial work: it enumerates all returned fields, explains the freshness field's null/status semantics, clarifies that sources prove the component was checked against real material, and notes the no-arguments list-everything behavior. It does not explicitly say the operation is read-only, but 'search' plus the absence of side-effect language makes that reasonably implicit.

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 long but information-dense. Every clause earns its place: return-field detail, freshness caveat, filter modes, and the no-args behavior. There is mild redundancy in phrases like 'for each match' and the very elaborate definition of sources, but no filler. The main purpose is front-loaded.

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?

Since there is no output schema, the description compensates by listing all return fields and their semantics, including freshness and sources. With only two optional parameters fully documented in the schema, the description is sufficient for an agent to call the tool correctly. Minor omissions like pagination or ordering are not critical for this discovery/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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the intent of the provides parameter — discovering components by what they do rather than knowing ids — and by documenting the behavior of calling with no arguments. These additions exceed the schema's literal property 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 starts with a specific verb and resource — 'Search the BotKelp component registry' — reinforced by the stack context 'Next.js/Supabase/Tailwind Lego blocks'. It clearly differentiates from the action-oriented siblings (create_project, apply_changes_to_repo, generate_scaffold) by framing itself as a discovery 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 gives clear usage context: filter by free-text or provides capability tags to discover components by what they do, and call with no arguments to list everything. It also warns to check freshness before relying on a component. However, it does not explicitly name alternative tools or describe when not to use this tool, so it stops short of a 5.

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