memory_import

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

No annotations are present, so the description carries full burden. It only states the tool imports files into memory, implying a write operation, but does not disclose whether it overwrites existing data, appends, or checks for duplicates. Potential side effects like memory state changes or performance impacts are not mentioned.

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 it omits essential details for a tool with four parameters and no schema descriptions. It could be improved by adding brief parameter explanations without becoming overly long.

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 tool's complexity (4 parameters, no output schema, no annotations), the description is insufficient. It does not explain the import process, how files are selected, or what the output/result looks like. The agent lacks context to use it safely or effectively.

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 0%, and the description provides no explanation of the four parameters (force, limit, source_id, all_sources). The agent has no guidance on their purpose or how to use them correctly, severely limiting effective 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 action (import) and the resource (changed Codex transcript JSONL files into memory). It specifies the file type and condition 'changed', which adds precision. However, it does not differentiate from sibling tools like memory_import_bundle or memory_context, which may also involve importing or setting memory 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?

No guidance is provided on when to use this tool versus alternatives such as memory_import_bundle or memory_update. The description does not mention prerequisites, limitations, or conditions under which this tool is appropriate or inappropriate.

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