search_knowledge

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

Discloses that tool returns chunks with source and snippet, instructs agent to synthesize answer and cite sources. Specifies query length limit (500 chars) and k range (1-10). No annotations present, so description fully covers behavioral expectations.

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, front-loaded with purpose, followed by parameter details and usage instruction. Every sentence adds value.

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 simple parameter set and no output schema, description adequately covers input, behavior, and output format. No gaps for effective tool use.

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?

Adds critical meaning beyond schema: query is natural language with max length, k is number of chunks with range. Since schema coverage is 0%, description provides all necessary parameter context.

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 semantic search over internal knowledge base with specific topics (MiCA, AML/KYC, custody, listing). Distinct from sibling tools which handle price, market history, and portfolio analysis.

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?

Implies usage for knowledge-based questions, and provides guidance on synthesizing answers and citing sources. However, no explicit when-not-to-use or alternative suggestions.

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