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

Annotations only say readOnlyHint=true and openWorldHint=true; the description adds genuinely new behavioral context: per-call pricing, auto-orientation of phone photos, metadata stripping, and the alternate fit modes. It does not cover auth/x402 mechanics or failure behavior, but it goes well beyond what the annotations disclose and does not contradict the read-only hint.

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?

A dense but front-loaded single sentence: capability and format matrix first, cost last. Every clause carries information, though cramming all operations into one run-on sentence slightly hurts scannability.

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 12 parameters, zero required, no enums and no output schema, the definition should at minimum explain that one of url/file_base64 must be supplied and how output is returned (base64 vs binary vs store links). Those gaps are left to the schema descriptions, so the definition is adequate but not self-sufficient.

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 67%, so most parameters are already documented in the schema. The description restates the fit modes (contain/cover/fill), rotate, grayscale and quality in prose but adds no format/unit detail beyond the schema, and it never clarifies the url vs file_base64 alternative despite neither being required.

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?

States a specific verb (convert, resize) plus the engine (ImageMagick) and enumerates accepted input and output formats, so the resource is unambiguous. It does not differentiate itself from close siblings such as image_edit, image_fast, image_pro or media_convert, so an agent cannot tell from the text alone which of those to prefer.

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 says what can be done but never when to choose this tool over the other image siblings, nor any prerequisite/exclusion. The only routing signal is the price line ($0.005 USDC via x402), which is cost information rather than use-case guidance.

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