memory_migrate_images

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

With no annotations, the description carries full burden. It discloses that the tool scans all memories, uploads images, and replaces data URIs. It also notes rate limiting (300s cooldown) and describes the dry_run mode. This is good behavioral disclosure, though it could mention whether changes are reversible.

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 concise (5 lines) and front-loaded with the core purpose. It then provides details on how it works, the dry_run parameter, return value, and rate limit—no wasted 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?

For a migration tool with one parameter and an output schema (mentioned in description returning a dict), the description covers the main aspects. However, it could mention potential side effects (e.g., irreversibility, need for R2 connection) or performance implications of scanning all memories.

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?

The input schema has only one parameter (dry_run) with no description. The tool's description adds clear meaning: 'If True, only report what would be migrated without making changes.' This fully explains the parameter's purpose, compensating for the 0% schema coverage.

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: migrating base64 images to R2 storage by scanning memories and replacing data URIs with R2 URLs. This verb+resource combination is specific and distinguishes it from siblings like memory_upload_image (which likely handles new uploads) and memory_update (general update).

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 when base64 images need migration, but lacks explicit when-not-to-use guidance or alternatives. It does not mention prerequisites (e.g., R2 configuration) or conditions when the tool should be avoided.

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