memory_upload_image

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

Since no annotations are provided, the description must disclose all behavioral traits. It mentions the upload action, return value, and organization by memory_id. However, it omits details about error handling, file size limits, overwrite behavior, or authentication requirements. It is adequate but not comprehensive.

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 at around 100 words and follows a clear structure: summary, parameter descriptions, and return value. It avoids fluff but could be slightly more streamlined. The docstring format is efficient and easy to parse.

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 simplicity (4 parameters, no annotations, output schema exists but not shown), the description covers the essential behavior: upload process, parameter roles, and return value. It adequately supports an agent in understanding the tool, though missing details about output schema structure could be a minor gap if the schema is rich.

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 0% description coverage, so the description adds necessary context. It explains that file_path is absolute, memory_id is for R2 organization, image_index has a default, and caption is optional. This meaningfully supplements the schema property names, though some parameters (like file_path) could still benefit from format hints.

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 uploads an image file to R2 storage and returns an r2:// reference URL. It specifies the resource (image file) and action (upload), effectively distinguishing it from sibling tools like memory_create or memory_store_document, which serve different purposes.

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 explains what the tool does but does not provide explicit guidance on when to use it versus alternatives. There is no mention of prerequisites, when not to use it, or how it compares to siblings like memory_migrate_images. The usage context is implied by the tool's purpose, but no direct guidance is given.

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