Cortex

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions extraction of specific content types but omits critical details: whether this is a read-only or write operation (though 'import' suggests writing), what permissions are needed, whether it overwrites existing data, error handling, or performance characteristics. The description provides some context about what gets extracted but lacks comprehensive behavioral transparency.

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 efficiently structured in two sentences that convey core functionality. The first sentence covers the main action, source, and destination. The second adds valuable detail about extraction content. There's minimal waste, though it could be slightly more front-loaded by mentioning extraction in the first sentence.

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 has 6 parameters with 0% schema coverage and no annotations, but does have an output schema, the description is moderately complete. It explains the core purpose well but leaves parameters completely undocumented. The output schema existence means return values don't need description, but the parameter gap and lack of behavioral context are significant omissions for a data import tool.

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 for 6 parameters, the description provides no information about any parameters. It doesn't explain what 'project', 'domain', 'min_importance', 'max_sessions', 'dry_run', or 'full_read' mean or how they affect the import process. The description fails to compensate for the complete lack of schema documentation.

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 specific action ('Import conversation history'), source ('from ~/.claude/projects/'), destination ('into the memory store'), and what gets extracted ('decisions, errors, architecture notes, and key insights from JSONL sessions'). It distinguishes itself from siblings like 'record_session_end' or 'sync_instructions' by focusing on historical import rather than real-time recording or synchronization.

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 implies usage when needing to import historical session data into memory, but provides no explicit guidance on when to use this versus alternatives like 'backfill_memories' or 'seed_project'. There's no mention of prerequisites, exclusions, or comparative context with sibling tools.

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