Capture context to memory

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

The description says 'capture and store' implying persistence, but lacks details on side effects (e.g., overwriting, limits, retrieval). Annotations are minimal (readOnlyHint=false, destructiveHint=false) and the description adds little beyond the basic 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 very concise at two sentences, with the core action front-loaded. It avoids unnecessary words, but could be slightly more structured (e.g., separating purpose from usage guidance).

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 complexity (10 parameters, nested objects, no output schema) and lack of annotations, the description is insufficient. It does not explain what 'capture' entails for retrieval, how required fields work, or any behavioral nuances. The agent lacks guidance on how the stored context can be accessed later.

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% coverage with descriptions for all parameters. The tool description does not add new information beyond the schema, but it provides context on event_type (by listing examples like 'decisions, insights, preferences') which aligns with the enum values.

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 captures and stores context from conversations. The title reinforces this. It distinguishes from siblings like memory_create_doc and session_remember by focusing on persisting general context, though it could be more specific about 'context' meaning conversation content.

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 examples of when to use it (persist decisions, insights, preferences, or important information) but does not explicitly state when not to use it or how it compares to alternatives like session_capture_lesson or memory_create_doc.

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