Memory Add

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

With no annotations, the description carries the full behavioral burden. It notes that an id is returned but says nothing about persistence lifetime, duplicate handling, whether metadata is indexed/searchable, or any permissions or rate limits for a write operation.

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?

Two short sentences with the core action front-loaded and no filler. It is efficient, though the return-value sentence is partly redundant given an output schema exists.

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 output schema covers the return value, but with no annotations, 0% parameter coverage, and a mutation that stores user data permanently, the definition omits the ingestion semantics and sibling routing an agent needs to call this safely and correctly.

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 nothing documents 'text' or 'metadata'. The description only implies a free-form string ('memory chunk') and gives no hint about what metadata is for or how it affects later retrieval, leaving the schema gap unclosed.

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?

States a concrete verb and resource ('Add ... memory chunk'), so an agent can tell it is the write path in a memory_* family. However, it does not differentiate itself from siblings (memory_update, memory_search) or explain what 'ad-hoc' means and how it differs from other insertion paths.

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 when-to-use guidance and no mention of alternatives. An agent must infer on its own that this is for creating a new free-form memory rather than updating an existing one via memory_update, which is a real ambiguity given the sibling names.

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