RecallNest

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

With no annotations provided, the description carries full disclosure burden. It successfully reveals the side effect nature ('persists up to 20 entries'), the deduplication behavior, and the entry limit. Minor gap: does not specify failure behavior (partial vs atomic) or return value structure.

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 efficiently structured sentences with zero waste: first states purpose, second discloses behavioral limits, third provides usage guidelines. Front-loaded with the core verb and resource.

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 zero schema descriptions, no annotations, no output schema, and complex nested parameters (memories array with enum fields), the description is incomplete. It covers the batch operation concept well but leaves critical data structure semantics (scope usage, category types, importance scale) undocumented.

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 description coverage is 0%, requiring the description to compensate. It explains the '20 entries' limit (mapping to memories.maxItems) and deduplication, but fails to explain required parameters 'scope' (namespace semantics) and 'source' (provenance), or the memory object fields (category enum, importance range).

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 specific action (Store multiple memories), mechanism (single call with deduplication), and scope (batch operation). It explicitly distinguishes itself from the sibling tool 'store_memory' by mentioning it is 'more efficient than repeated store_memory calls'.

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?

Provides explicit when-to-use guidance ('when you have several facts to store at once') and clearly names the alternative ('repeated store_memory calls'), enabling the agent to make correct routing decisions between batch and single-item storage.

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