Transfer Memories

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: that import 're-assigns IDs' and 'skips duplicate topicKeys', which are crucial implementation details. However, it doesn't mention permission requirements, rate limits, error conditions, or what happens during export beyond format options.

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 perfectly front-loaded with the core purpose, then efficiently details each action's behavior. Every sentence earns its place by adding specific operational details. No wasted words or redundant information.

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 tool with 3 parameters, 100% schema coverage, but no annotations or output schema, the description provides adequate coverage of the core functionality. However, it lacks information about return values, error handling, and broader system context that would be helpful given the data transfer nature of the 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 description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it clarifies that 'format' applies only to export (with default), specifies what 'data' contains ('JSON string from a previous export'), and explains behavioral implications of import. This elevates the score above baseline.

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 ('export or import project memories') and distinguishes it from siblings by focusing on data transfer operations rather than consolidation, deduplication, or other memory management functions. It explicitly mentions the resources involved ('observations and sessions').

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 provides clear context for when to use each action ('export' vs 'import') and mentions format options, but doesn't explicitly state when NOT to use this tool or name specific alternatives among the sibling tools. It distinguishes between the two modes but lacks broader usage guidance relative to other tools.

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