search

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

Despite no annotations, description reveals key behaviors: outputs summaries (not source), hybrid method, ranked ordering, no snippets, returns several candidates. This covers main behavioral aspects for a search tool.

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?

Two sentences with zero wasted words. Each sentence adds distinct value: first defines the hybrid nature and output type, second specifies behavior and alternative. Ideal conciseness.

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?

While it addresses purpose and one sibling, it doesn't cover the broader toolset context (e.g., when to use get_context vs. search) or return format details. Given the sibling count and no output schema, more context would improve completeness.

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 only 50% (k described, query not), and description adds no further parameter information. It doesn't clarify query syntax or how k affects results, failing to compensate for the schema gap.

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?

Description clearly states it performs hybrid search returning ranked summaries (not source), and distinguishes itself from the sibling 'locate' by noting it returns multiple candidates. This gives a specific verb+resource with clear scope.

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 advises preferring 'locate' when only one item is needed, providing a clear alternative. Implies usage for multi-result scenarios, but does not contrast with other siblings like get_context or get_source.

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