memora

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully communicates the scope (scans all memories), mutative nature (replacing data URIs), rate limiting (300s cooldown), and dry-run capability. Missing details on failure handling, reversibility, or concurrency safety.

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 well-structured with a clear summary sentence followed by implementation details and docstring-style Args/Returns sections. The rate limit warning is appropriately placed. Minor verbosity in the Args header is acceptable given the schema limitations.

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 the tool's complexity (destructive migration with rate limiting) and lack of annotations, the description adequately covers the critical aspects: operation scope, parameter behavior, return value structure, and rate limits. It appropriately omits detailed return value schemas since an output schema exists.

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 schema has 0% description coverage (only title 'Dry Run'), so the description's Args section provides essential semantic meaning: 'If True, only report what would be migrated without making changes.' This fully compensates for the schema's lack of documentation.

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 specific action (migrate), source (existing base64 images), destination (R2 storage), and mechanism (scans all memories, replaces data URIs). It effectively distinguishes this from generic upload operations, though it doesn't explicitly contrast with sibling tool `memory_upload_image`.

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 through the `dry_run` parameter explanation (test before migrating), but lacks explicit guidance on when to choose this tool versus alternatives like `memory_upload_image`. It describes what happens but not the decision criteria for selecting it.

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