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

Even with no annotations, the description discloses the core behavior: reading GPS from EXIF and converting it to map links. It does not explain how the input is supplied, whether the tool fetches remote images, or what edge cases exist, leaving meaningful gaps beyond the core transformation.

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 a single economical sentence, which is appropriate for a simple tool. However, the 'Image GPS:' prefix repeats the title, and 'feeds globe' adds little clarity, making it terse rather than tightly structured.

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 do not need to be described, but the input semantics, expected image source, and usage boundaries are all underspecified. For an agent deciding how to invoke this tool, the description leaves too much to inference.

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 describes 'q' only as a string with an empty default and no further explanation, and the description never mentions q or its format. The phrase 'from EXIF' weakly implies that q is an image, but with 0% schema coverage the description fails to meaningfully clarify the parameter.

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 clear transformation: extract GPS coordinates from image EXIF and produce map links. This is specific enough to separate it from nearby image-metadata tools like imageexif or imagemeta. It loses the fifth point because there is no explicit verb and the phrase 'feeds globe' is vague.

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 the use case: when you need GPS coordinates and map links from an image's EXIF data. However, it gives no explicit guidance about when to choose this tool over imageexif or other image-analysis siblings, and it does not mention acceptable input formats.

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