velixar_multi_search

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

With no annotations, the description carries full burden. It reveals key behaviors: deduplication, temporal awareness, merging, and strategies (union, intersection, weighted). It does not cover rate limits, authentication, or error handling, but the disclosed behaviors are sufficient for typical use.

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 well-structured sentences. The first sentence front-loads the core purpose and features. Every word earns its place; no fluff.

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?

No output schema is provided, so the description should clarify return format. It mentions 'merged results by default' but does not detail the structure or fields. Temporal awareness is named but not explained. With 6 parameters, the description covers usage but lacks depth on outputs.

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 baseline is 3. The description adds marginal value by example (setting merge:false) and mentions strategy, but the schema already describes all parameters adequately.

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 from multiple angles simultaneously with deduplication and temporal awareness, and specifies it returns merged results by default. It distinguishes itself from sibling tools like velixar_search (single query) and velixar_batch_search (which it replaces).

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 explicitly tells when to set `merge: false` for per-query results and notes this replaces velixar_batch_search, guiding the agent on alternatives. However, it does not explicitly state when not to use the tool or provide other exclusions.

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