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

Goes well beyond the annotations by disclosing concrete behavior: private/local addresses are refused, decoded input is capped at 10 MB, gps-only stripping preserves other JPEG tags, and non-JPEG formats are re-encoded and lose every tag. These are exactly the side-effect details an agent needs and that readOnlyHint/idempotentHint cannot convey.

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?

Six short sentences, front-loaded with purpose and mode selection before constraints. Slight redundancy in restating the action/scope enums that the schema already declares, but no filler or buried caveats.

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?

An output schema exists so return values need not be explained, and the description covers input transport, size limit, SSRF refusal, and format-specific strip behavior. Remaining gap is that it never says whether stripping returns a modified file or how the result is delivered.

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%, and the description adds real meaning: 'Send base64 or a public URL' clarifies the file shape, and 'Other formats are re-encoded, which drops every tag' explains the scope enum's practical consequence beyond the schema's wording. Minor duplication of the action/scope enumerations, but net additive.

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+resource ('Read EXIF tags, including GPS, or strip them') and distinguishes the two operating modes up front. No sibling tool in the list covers metadata reading/stripping, so the boundary is unambiguous.

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 how to choose between the action/scope modes, which is useful, but never states when to pick this tool over adjacent image tools (compress_image, convert_image, read_image_text) or any prerequisite such as requiring a public URL first. Usage is implied rather than routed.

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