memory_migrate

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

No annotations provided, so description carries full burden. Transparently discloses behavior: discovers files, splits by markdown headers, returns sections, and explicitly states it does NOT store anything. Also mentions file locations and return format.

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?

Description is concise, three short paragraphs each adding value. Front-loaded with purpose, then usage details, then explicit non-store disclaimer. No redundant sentences.

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 single optional parameter and no output schema, the description is complete. Explains input behavior, output format (sections split by headers), and follow-up actions. Addresses complexity adequately.

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?

Input schema has no description for the sole parameter (0% coverage). Description adds significant meaning: explains behavior with no path (discover all) vs with a path (read specific file). This compensates fully.

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?

Description clearly states the tool discovers and reads memory files (CLAUDE.md, auto-memory) for migration, and distinguishes from siblings like memory_store by explicitly stating it does not store. The verb 'discover and read' is specific.

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 tells when to use (migration context) and when not to (skip instructions). Provides clear instructions: review sections, call memory_store for knowledge. Includes path vs no-path distinction.

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