Memory store

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

Annotations already indicate this is a mutation (readOnlyHint=false, idempotentHint=false), and the description adds that the store is persistent and that the unit of work is a single observation. However, it does not disclose what happens on duplicate stores, whether entities are auto-created, or whether observations append or replace. Given the simple scope and non-destructive annotations, this is adequate but not rich.

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?

One sentence, no waste, action front-loaded, parenthetical for context. The description is appropriately sized for a simple three-parameter tool.

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?

The core operation is clear enough to invoke with the required parameters, and an output schema exists so return values are covered. However, with 0% schema coverage, the description should have explained entity_type or at least signaled its optional role. It also lacks any hint about knowledge-graph behavior such as deduplication or entity creation. Functional but not fully complete.

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 clarifies 'entity' as the target and 'observation' as the content, but it omits 'entity_type' entirely and provides no additional meaning for any parameter. The optional entity_type parameter remains undocumented.

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 a specific verb ('Store'), a direct object ('one observation'), and a target ('an entity'), with the parenthetical 'persistent knowledge graph' adding context that distinguishes it from read/delete/link siblings. It is immediately clear what the tool does and how it differs from memory_recall, memory_forget, and memory_link.

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?

There is no explicit guidance about when to use this tool versus its siblings. The agent must infer usage from the name and sibling list; nothing says 'use this when persisting a new fact' or contrasts it with memory_recall for retrieval.

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