import_memories

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

Annotations already indicate readOnlyHint=false, destructiveHint=false. Description does not contradict but adds minimal behavioral context (e.g., mode='merge' in example). No mention of side effects or atomicity.

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?

Two sentences plus actionable guide. Front-loaded with purpose, no redundancy. Every sentence adds value.

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?

Provides purpose and when-to-use, but lacks parameter explanation (mode values, data format specifics). Output schema exists but not described. Adequate for simple cases but incomplete for complex usage.

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 0%, so description must compensate. It mentions 'data' formats (JSONL or list) and gives mode='merge' example, but does not explain mode values or data structure details. Inadequate for precise 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?

Title says 'Import Memories', description states 'Import memories from JSONL data or a list of objects' - clear verb+resource+format. Differentiates from sibling add_memory (single) by implying bulk operation, though not explicit.

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?

ACTION GUIDE states 'when to use: Use when restoring from a backup or migrating data' - explicit context. No mention of when not to use or alternatives, but sufficient for common cases.

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