memento_remember

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

No annotations are present, so the description must disclose behavioral traits. It only lists actions without explaining effects, side effects, permissions, or other important behaviors. For a tool with 12 parameters, this is insufficient.

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 very short (two sentence fragments) and lacks structure. While concise, it fails to organize information effectively, making it harder for an agent to parse.

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?

With 12 parameters, no output schema, no annotations, and a sparse description, the tool is severely under-documented. The description does not cover parameter semantics, return values, or behavioral traits, making it inadequate for correct invocation.

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 only 8% (only 'text' has a description). The description does not explain the purpose or usage of the other 11 parameters, leaving the agent without needed context for invocation.

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 'Memory operations' and lists actions (add, consolidate, share, evaluate, hit), which gives a general sense but lacks a specific verb or clear scope. It distinguishes from siblings only by being a catch-all for multiple actions, but does not specify what the tool does overall.

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 when-to-use guidance is provided. The description does not indicate when to use this tool versus sibling tools like memento_search or memento_kg, leaving the agent without context for selection.

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