memorize

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

With no annotations, the description carries the full burden of disclosure. It only says 'store' without explaining behavior like whether an existing key is overwritten, persistence scope, or any side effects. This is a mutation tool, and zero behavioral detail makes it insufficient for the agent to anticipate outcomes.

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?

A single sentence that is direct and front-loaded. Every word earns its place, and there is no redundancy or filler.

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 tool is a simple key-value store, but the description lacks essential context: no mention of overwrite behavior, persistence, potential return values, or how the memory relates to the project lifecycle. Since there is no output schema and no annotations, the description alone is insufficient for an agent to fully understand the consequences of calling this tool.

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 minimally relates 'key-value' to the parameters, implying the key is the identifier and the value is the stored content. However, it adds no detail on format, constraints, or valid values, leaving the schema types as the only real documentation.

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 clearly states a specific action ('Store') on a specific resource ('key-value memory for the project'). It distinguishes itself from siblings like 'recall_context' (which presumably retrieves memory) and generation tools by indicating a write operation for project memory.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'memorize_endpoint' or 'recall_context'. It neither states prerequisites nor when not to use it.

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