jambavan_memory_store

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

Discloses idempotency, return value, and format. No annotations exist, so description carries full burden. Lacks details on side effects (e.g., does it trigger indexing?), error handling, or permission requirements.

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?

Four sentences, front-loaded with main purpose, each sentence adds essential information. No superfluous text.

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?

Covers key behavior (write, idempotent, return ID), format, and parameter defaults. Does not explain return value structure beyond ID, but acceptable for a store tool without output schema.

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?

With 100% schema coverage, baseline is 3. Description adds value by explaining scope defaults, idempotency, and portability beyond the schema's field descriptions.

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?

Description clearly states the tool persists a memory as an OKF concept document, with specifics on format (markdown + YAML) and idempotency. It distinguishes from sibling read-only memory tools like jambavan_memory_get or jambavan_memory_recall.

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?

Implies usage for storing or updating memories, including overwrite behavior. However, it does not explicitly state when not to use it (e.g., for read operations) or mention alternative tools.

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