add_memory

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

Describes the action and return value, but with no annotations, it lacks details on side effects, persistence, or idempotency. Adequate but could be more thorough.

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?

Well-structured with a short main description, bulleted use cases, and clear Args section. Every sentence is informative and no wasted words.

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?

Covers purpose, usage scenarios, parameter details, and return value. Given the complexity and output schema, it provides all necessary context 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?

Given 0% schema coverage, the description compensates fully by explaining each parameter with examples and hints, such as listing category options and tag formatting, which adds significant value.

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 'Store a new memory/learning for future reference' and provides specific use cases, distinguishing it from related tools like search_memories or list_memories.

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?

Explicitly says when to use (remember standards/patterns from PRs, code reviews, etc.) and lists common use cases. Does not mention when not to use or alternatives like remember_from_pr_comment, but still provides strong guidance.

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