Memory Store Batch

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

The description adds context beyond annotations, mentioning atomic transaction, deduplication via fingerprint and semantic similarity, and returning counts and per-row errors. Since annotations only mark readOnlyHint=false and destructiveHint=false, the description effectively discloses write behavior and error handling.

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 is a single sentence with three concise clauses: batch size and atomicity, deduplication method, and return values. It is front-loaded with the main action and contains no redundant information.

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 and the presence of an output schema (which covers return values), the description covers key aspects: batch limit, atomicity, dedup, and error reporting. It does not detail parameter purposes but the schema provides structure. Slightly lacking in parameter guidance, but overall adequate.

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%, so the description must compensate. It mentions deduplication and semantic similarity, hinting at fields like fingerprint and dedup_threshold, but does not explain the many other fields in the memories array. The description provides overall context but insufficient detail for each parameter.

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 'Store up to 100 memory entries in a single atomic transaction', specifying verb, resource, batch size, and transaction behavior. It distinguishes from sibling tools like localnest_memory_store by emphasizing batch atomicity and deduplication.

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 description implies use for batch storage with deduplication, which is clear. However, it lacks explicit guidance on when not to use or alternatives like localnest_memory_store for single entries. The batch nature and atomicity provide sufficient context for most agents.

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