kb_search

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds 'READ-ONLY' and 'limited block traversal', which are useful context about safety and search scope. However, it does not describe result format, pagination behavior, or what happens when limits are hit.

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, front-loaded phrase that immediately signals READ-ONLY and the core search function. No wasted words, and it effectively communicates the essence of the tool.

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 there are 6 parameters and no output schema, the description is somewhat sparse. It hints at limited traversal but does not explain return values, sorting, or how to interpret results. The schema covers parameters well, so the description's brevity is partially mitigated.

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 itself provides no additional parameter-level meaning beyond what the schema already documents, which is detailed and self-explanatory.

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 tool searches for text in titles and content of Landing knowledge base pages, with a specific mention of limited block traversal. This gives a specific verb+resource+scope, though it does not explicitly differentiate from similar sibling tools like kb2_search.

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?

No guidance is provided on when to use this tool over alternatives such as kb2_search or kb_list. The description lacks any context about prerequisites or exclusions, and the only recommendation (site_id for large portals) appears in the schema, not the description.

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