sage_recall

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

With no annotations, the description reveals default local search, federated behavior with 'allowed live read', and caller-safe delegation. Could mention read-only nature more explicitly, but it's sufficiently transparent.

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?

Three concise, front-loaded sentences with zero waste. Each sentence adds essential information: purpose, federated usage, and prerequisite tool reference.

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 core functionality and federated mode well. Lacks description of return format, but parameter descriptions cover details. Adequate for a search tool with rich parameter descriptions.

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%, so baseline is 3. Description adds value by explaining federated parameter usage and federate_chains workflow, going beyond parameter descriptions.

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 memories by semantic similarity, with specific verb 'search' and resource 'memories'. It distinguishes from siblings like sage_federation (discovery) and other non-search tools.

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?

Explicitly explains when to use federated mode (when a domain is shared) and directs to sibling sage_federation for discovery, providing clear when-to-use and when-not-to-use guidance.

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