get_image_info

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

With no annotations, the description carries the full burden of transparency. It discloses the return structure in detail, including a success flag and optional fields (e.g., gps if available), giving a good sense of the operation's output. It does not explicitly state the operation is read-only or describe error conditions, but the 'get' verb and success flag imply a safe, well-defined behavior.

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 front-loaded with the core purpose, followed by structured Args and Returns sections. Although it lists many metadata fields, this is necessary because there is no output schema to document the return value, so every detail earns its place.

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?

Without an output schema or annotations, the description must be self-sufficient, and it is. It covers input semantics, return format comprehensively, and notes optional availability of certain fields. The absence of explicit error handling is mitigated by the success flag, making it complete for a simple get-by-id tool.

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 only defines image_id as a required string with no description (0% coverage). The description compensates by explaining that it is a 'Unique identifier for the image (obtained from search results)' and clarifies how it is used to fetch the metadata, adding crucial meaning beyond the schema.

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 opens with a specific verb 'Get' and resource 'detailed metadata for a specific image', then enumerates metadata categories (EXIF, camera settings, location, file details). This clearly distinguishes it from siblings like search_images, which finds images.

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 provides clear context by stating that image_id is 'obtained from search results', implying usage after a search. However, it does not explicitly mention when not to use this tool or name alternative tools such as get_archive_stats, leaving room for ambiguity.

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