mcp_engram_batch_remember

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

No annotations provided, so description carries burden. Mentions applying 'thermodynamic CRS gating' (some internal behavior) and describes output as confirmation of committed concepts. Lacks details on potential partial failures or error handling.

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?

Three focused sentences, each serving a clear purpose: behavior, usage, output. No fluff, efficient communication.

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, behavior, and output. Lacks details on batch size limits or error scenarios, but given simplicity of the tool (one parameter, no output schema), it is reasonably complete.

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 fully describes the 'entries' parameter (array of {concept, text}). Description adds context about 'distinct texts' and 'separate blocks' but does not significantly supplement the schema for parameter usage. Baseline 3 due to high schema coverage.

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?

Clearly states the tool encodes and stores multiple distinct texts as separate HolographicBlock memories, which distinguishes it from the sibling tool mcp_engram_remember that handles single entries. The verb 'batch remember' is well explained.

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 recommends use for several unrelated facts/snippets and highlights performance gain over sequential calls. No explicit when-not-to-use, but the context implies it's not for single items.

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