recall_relevant

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

Describes the algorithm (SimHash + multi-dimensional scoring with feedback loop) but lacks disclosure of side effects (e.g., whether scores are persisted) or permission requirements. No annotations provided, so description carries full burden.

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 short paragraphs with essential info. No redundant sentences. Front-loaded with purpose, then method.

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?

Output schema exists, so return values are covered. However, considering no annotations and many sibling tools, a brief statement on when to use this over exact search 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?

Adds meaning to parameters: query is search query, top_k is number of results. Schema coverage is 0%, so description compensates well. Could specify query format or top_k constraints.

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 the tool performs semantic recall of stored fragments using SimHash and scoring. While it doesn't explicitly distinguish from siblings like vault_search or entroly_retrieve, the mention of feedback loop sets it apart.

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?

No guidance on when to use this tool versus alternatives like vault_query or entroly_retrieve. Missing context for when semantic recall is preferred over exact search.

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