memory

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

With no annotations, the description carries full burden. It discloses destructive operations (forget, delete, etc.) and explains protections (rules/mistakes from category delete). However, it does not address authentication needs, rate limits, or failure behavior, leaving gaps.

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 long, unstructured list that is not concise. It could be organized into categories or groups. While front-loaded with 'Memory operations', it still reads as a wall of 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?

Given the tool's complexity (20 operations, 17 parameters), the description is fairly complete in covering each operation's behavior. However, it lacks information about return values (no output schema) and error conditions, making it less than fully comprehensive.

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 100%, so baseline is 3. The description adds minor context by associating parameters with specific operations, but largely repeats what the schema already states. It does not significantly deepen understanding beyond the schema.

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 enumerates each operation with a brief explanation, making it specific about what the tool does across multiple memory management tasks. However, the lack of a title and the overwhelming list slightly reduce clarity. It is distinguishable from siblings by being a general memory tool.

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 explicit guidance on when to use this tool versus other sibling tools (e.g., context, convention). The description only lists operations without providing context on when each operation is appropriate or when to choose an alternative tool.

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