Memory Capture Event

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

The description mentions 'auto-promote meaningful events,' implying a selection mechanism, but provides no details on how promotion works, what side effects occur (e.g., state changes, deletions), or any rate limits. Annotations (readOnlyHint=false) indicate mutability, but the description does not elaborate on behavioral traits beyond the summary.

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 single sentence, which is concise but overly brief given the tool's complexity. It front-loads the core action but omits necessary details, making it less efficient for agent comprehension. A slightly longer description would improve clarity without sacrificing conciseness.

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?

Despite having an output schema, the description is woefully incomplete for a tool with 18 parameters, nested objects, and no schema descriptions. It fails to explain return values, parameter usage, or the auto-promotion logic. An agent cannot fully understand how to invoke this tool correctly from the description alone.

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?

With 0% schema description coverage and 18 parameters (many with enums and nested objects), the description adds no meaning to any parameter. It does not mention any parameters, defaults, or constraints. The agent must rely solely on schema structure, which is insufficient for correct invocation.

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: 'Ingest a background work event and auto-promote meaningful events into durable memory.' It specifies the verb (ingest, auto-promote) and resource (background work event, durable memory), distinguishing it from siblings like localnest_memory_store (explicit storage) and localnest_memory_events (retrieval).

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 alternatives. There are many sibling memory tools (e.g., memory_store, memory_events, memory_recall), but the description does not indicate use cases, prerequisites, or when not to use it. This lack of direction forces the agent to infer from context.

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