RecallNest

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It earns credit for explicitly stating 'Side effect: writes an export artifact file,' which is critical for an agent to understand the file-system impact. However, it omits other important behavioral details like idempotency, overwrite behavior, or what the function returns (file path vs. content).

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 consists of three efficiently structured sentences: the action, the side effect, and the usage guideline. Every sentence earns its place with no redundant or tautological content, and it is appropriately front-loaded with the core verb.

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 the tool's complexity (7 parameters, no annotations, no output schema), the description provides the minimum necessary context by mentioning the file write side effect. However, it lacks details about the return value (e.g., file path confirmation) and does not explain how the 'distilled' content is selected from the memory store, leaving gaps for a multi-parameter export operation.

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?

The input schema has 100% description coverage, establishing a baseline of 3. The description reinforces the 'format' parameter by mentioning 'markdown or JSON' and implies the 'query' parameter with 'knowledge on a topic,' but does not add semantic context beyond what the schema already provides for 'scope', 'profile', or 'limit'.

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 action (Export), the resource (distilled memory briefing), and the output format (markdown or JSON file on disk). It effectively distinguishes this from sibling tools by emphasizing the file-on-disk aspect, though it could clarify its relationship to 'distill_memory' explicitly.

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 phrase 'Use when you need an offline-readable snapshot of knowledge on a topic' provides clear context for when to invoke this tool. However, it lacks explicit guidance on when NOT to use it (e.g., for in-chat retrieval) or named alternatives like 'brief_memory'.

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