remember

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

With no annotations, the description must disclose side effects, persistence, overwrite behavior, and similar traits. It only states 'Store a memory' without revealing whether this creates a new record, overwrites existing ones, or requires specific preconditions. The parenthetical types are already reflected in the schema enum, adding no extra transparency.

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 a single short sentence with no redundancy and is front-loaded. However, for an 8-parameter tool, it is arguably too terse to be 'appropriately sized,' though every word earns its place.

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?

Given 8 parameters, no annotations, and no output schema, the description is drastically insufficient. It lacks return value information, parameter semantics, and usage context, making it incomplete for an AI agent to invoke 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% and the description mentions no parameters, including the required 'content'. It does not explain the meaning of cues, affect, confidence, importance, or evidence_count, failing to compensate for the schema's lack of descriptive text.

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 uses the specific verb 'Store' with resource 'memory' and notes types '(episodic or semantic)', clearly distinguishing from retrieval tools like recall and forget. However, it does not explicitly distinguish from the sibling 'remember_turn', leaving a slight ambiguity.

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 is provided on when to use this tool versus alternatives or exclusions. The only hint is 'Store a memory,' which implies usage but does not state conditions, and siblings like remember_turn suggest an alternative without any distinction.

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