Search Knowledge

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

Annotations already indicate readOnlyHint and destructiveHint, so the safety profile is covered. The description adds that search is 'semantic' and across 'all entries and documents', but does not clarify result pagination or format. Bar is lowered by annotations, so score reflects adequate but minimal added context.

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 sentence of 14 words, front-loading the core purpose. Every word is necessary, with no redundancy or extra detail.

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 no output schema, the description should explain what the tool returns, but it only says 'to find relevant information'. It does not specify the form of results (e.g., entry IDs, scores, content). Sibling differentiation is absent. Complexity is low, so missing return format is a gap.

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 100%, and the description does not add meaning beyond parameter names and displayed descriptions. No extra details about query format, id constraints, or limit behavior are provided.

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 performs 'semantic search across all entries and documents in a knowledge base', using a specific verb and resource. It distinguishes from siblings like list_kb_entries or search_contacts.

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 implies use for semantic search but provides no explicit guidance on when to use this tool versus alternatives like list_kb_entries or semantic_search_contacts. No when-not-to-use or contexts are mentioned.

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