Memory Store

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

Annotations are all false, so the description must provide behavioral context. 'Durable' implies persistence but no details on overwrite behavior, concurrency, or side effects. With 18 parameters and no additional behavioral disclosure, transparency is low.

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 extremely concise at 6 words, but this brevity is detrimental given the tool's complexity. It is under-specified rather than efficiently informative.

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?

For a tool with 18 parameters, nested objects, enums, and an output schema, the description provides virtually no context. It omits return value info, usage scenarios, and parameter interrelationships, making it severely incomplete.

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%, yet the description adds zero parameter information. The schema has 18 parameters with many enums and nested objects, but the description does not explain their purpose or usage, failing to compensate for the coverage gap.

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 states 'Store a durable local memory entry,' indicating the verb 'Store' and resource 'memory entry'. However, it does not differentiate from sibling tools like localnest_memory_store_batch, localnest_memory_update, etc., making it only moderately clear.

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?

No guidance on when to use this tool versus alternatives (e.g., memory_store_batch, memory_update). The description lacks any context about prerequisites or typical use cases.

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