mcp_engram_export

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

Describes the output format and content (JSON string with blocks and identifiers), implying it is a read operation. Without annotations, it partially reveals behavior but could be more explicit about side effects or lack thereof.

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 concise with clear labeling (BEHAVIOR, USAGE, OUTPUT). Every sentence adds value without unnecessary detail.

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?

For a simple tool with one optional parameter and no output schema, the description adequately covers purpose, usage, and output. Minor gap: it does not mention namespace scope or error conditions.

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 coverage is 100%, and the parameter min_crs is already well-described in the schema. The description adds minimal context ('filtered by minimum CRS'), which is redundant.

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 serializes the active memory manifold into a portable JSON array, with optional filtering. The verb 'serializes' is specific, and the usage context distinguishes it from sibling tools like import.

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 states when to call: for backup, migration, or synchronization. However, it does not mention when not to use or provide alternatives, though the sibling 'import' implies the inverse.

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