Cortex

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: idempotency through hash tracking, automatic concept linking, and processing constraints ('already-processed session files'). It doesn't mention permissions, rate limits, or error handling, but provides solid operational context for a backfill operation.

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 concise sentences with zero waste: first states core function, second explains idempotency mechanism, third describes value-add (automatic linking). Each sentence earns its place by adding distinct, valuable information. Perfectly front-loaded with the primary purpose.

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 5-parameter tool with no annotations but an output schema, the description provides good operational context about what the tool does and its behavioral characteristics. It doesn't explain parameters or return values, but the output schema handles returns, and the description gives enough context for an agent to understand the tool's role in the memory system.

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 5 parameters, the description adds no explicit parameter information. However, it implies parameter semantics through context: 'auto-import' suggests batch processing, 'tracks already-processed' relates to idempotency parameters, and 'historical work' suggests scope parameters. This provides meaningful context despite no direct parameter 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 tool's purpose with specific verbs ('auto-import', 'tracks', 'links') and resources ('prior Claude Code conversations', 'memory store', 'historical work', 'core concepts'). It distinguishes from sibling tools like 'import_sessions' by emphasizing automatic linking to concepts and idempotent processing.

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 for importing historical conversations automatically, but doesn't explicitly state when to use this vs. alternatives like 'import_sessions' or 'seed_project'. It mentions idempotency which suggests it's safe for repeated runs, but lacks clear when/when-not guidance or prerequisites.

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