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

The description adds substantial behavior beyond the annotations: a 10 MB limit, preserved formats for JPEG/PNG/GIF/WebP/AVIF, SVG conversion to PNG at 2x size, and refusal of SVGs containing scripts or external links. These details are consistent with the non-destructive write and open-world annotations.

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 four tightly written sentences: purpose first, then limits and format behavior, then the intended use case. Every sentence contributes useful information with no repetition or wasted phrasing.

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?

With no output schema, the description still states that the tool returns the uploaded URL. It also covers size, format handling, SVG restrictions, and the intended external-image use case, leaving no critical gap for an agent to call it correctly.

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 is already 100%, so the base expectation is 3. The description adds meaningful constraints for the url parameter, including size and accepted image formats, though it does not add anything about the token parameter beyond what the schema already explains.

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 states a specific verb and resource: copy an image from a URL into miow's store and return the resulting URL for a pictures block. This clearly distinguishes the tool from generic block or page operations in the sibling list, even without naming a specific alternative.

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?

It gives clear usage context: use this for an image hosted on someone else's server, which may move or vanish. It does not explicitly state when not to use it or name alternative tools, so it falls short of a full 5.

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