beeboo_knowledge_search

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Search' implies a read operation, it doesn't specify important behavioral aspects like whether this is a real-time search, if there are rate limits, authentication requirements, result format, or pagination behavior. The mention of 'semantic search' is helpful but insufficient.

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 single, efficient sentence that communicates the essential information without any wasted words. It's appropriately sized for a single-parameter search tool and front-loads the core functionality.

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 search tool with no annotations and no output schema, the description is inadequate. It doesn't explain what kind of results to expect, how results are ranked, whether there are limitations on query complexity, or how to interpret search results. The mention of 'semantic search' is the only contextual element provided.

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?

The input schema has 100% description coverage, with the single parameter 'query' well-documented as accepting natural language. The description adds minimal value beyond the schema by mentioning 'semantic search' which contextualizes the query parameter, but doesn't provide additional syntax or format details.

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 the action ('Search') and target resource ('BeeBoo knowledge base for information'), with the method 'using semantic search' providing specific implementation detail. However, it doesn't explicitly differentiate from sibling tools like 'beeboo_knowledge_list' which might also retrieve knowledge base content.

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 provides no guidance on when to use this tool versus alternatives like 'beeboo_knowledge_list' or 'beeboo_knowledge_add'. There's no mention of appropriate contexts, prerequisites, or exclusions for this search functionality.

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