recall

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

Describes return structure (ranked memories, open items count) and query hint. Lacks detail on budget_tokens behavior (e.g., truncation) and error handling. No annotations to supplement.

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 sentences, front-loaded with purpose and usage, no wasted words. Efficient and clear.

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: what it retrieves, when to use, query hint. Missing explanation of 'types' and specific behavior under token limit. Output schema exists but not detailed.

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?

Explains query parameter well ('few keywords'). Mentions token budget generically. Does not describe 'types' parameter or default/behavior of budget_tokens, partially compensating for 0% schema description coverage.

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 the verb (retrieve), resource (long-term memories), and context (current task). Distinguishes from siblings like 'remember' (store) and 'list_open'.

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 says 'Call this at the START of any task before doing work', providing strong when-to-use guidance. Does not mention when not to use or alternatives.

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