Import memory passport / data export

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

Annotations already indicate non-read-only, non-destructive, non-idempotent. Description adds that it imports as 'distilled memories' and returns import counts. Could elaborate on side effects (e.g., duplicate handling) but sufficient.

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?

Front-loaded with 'Bring context IN.' Uses bullet points for kinds, making it scannable. Five sentences is appropriate; no redundant information. Slightly verbose in middle lines but still clear.

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 full schema coverage and no output schema, description mentions return of import counts. Covers all param semantics and tool purpose. Lacks error handling details but overall adequate for a simple 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?

Schema covers both parameters with basic descriptions. Description enriches by showing default value for kind, listing enum options with explanations, and clarifying file is required. Adds meaningful context beyond schema.

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 it imports data from files using 'Bring context IN' and explains three kinds (passport, chatgpt, claude). Distinguishes from sibling mindmap_passport_export which does the reverse. Specific verb+resource.

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?

Description provides clear context: use when you have a passport file from another machine or exported chat files. No explicit when-not or alternatives, but the purpose is well-defined and siblings are listed separately.

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