mem_it

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Remember any content intelligently' and 'saving information,' but does not disclose whether this creates a record, whether it deduplicates, how 'intelligently' manifests, or what side effects may occur. This is a significant gap 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?

The description is two sentences with no wasted words. It front-loads the primary action ('Remember any content intelligently') and then clarifies the scope ('primary endpoint for saving information to mem.ai'), which is concise and effective.

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?

While the schema fully documents parameters and the purpose is clear, the absence of an output schema and annotations leaves unanswered questions about what the tool returns or any constraints (e.g., rate limits). The description is minimally viable but not rich enough to fully orient an agent for a generic save endpoint with no output schema.

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?

The schema has 100% description coverage for all four parameters, including explanations for 'input', 'context', 'timestamp', and 'instructions'. The description itself adds nothing about parameters, so with the schema already doing the heavy lifting, the baseline of 3 is appropriate.

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 the tool's purpose: 'Remember any content intelligently' with the explicit clarification that it is 'the primary endpoint for saving information to mem.ai.' This is a specific verb+resource combination and distinguishes it from sibling tools like get_note and create_note, which operate on notes and collections.

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 explicitly frames this as 'the primary endpoint for saving information to mem.ai,' which implies this is the go-to tool for general saving, as opposed to siblings that handle categories like notes or collections. However, it stops short of saying when not to use it or naming alternatives.

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