search

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

Discloses scoring formula, result count limit, and returned fields (source file, score, snippet). Lacks discussion on side effects or performance, but no annotations provided.

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?

Concise with structured args section, though the detailed formula may be more than needed for typical usage.

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?

Covers key aspects: search action, algorithm, parameters, and return format. Lacks pagination details but adequate for basic use given output schema existence.

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?

With 0% schema coverage, description fully explains query (natural-language or keyword) and k (max results, default 5), adding necessary meaning.

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?

Clearly states search action on indexed folder, specifies retrieval method (ColBERT MaxSim), and output format. Distinguishes from sibling index_folder.

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?

Implied usage for querying vs. indexing but no explicit when-to-use or alternatives compared to index_folder.

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