inspect_image_metadata

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

No annotations are provided, so the description carries the burden. It implies a read-only operation ('Inspects') and describes the return as a 'Diagnostic audit', which is useful. However, it doesn't explicitly state that it makes no modifications, or mention any permissions or edge cases like missing files or unsupported formats. The added detail about the output partially compensates but doesn't fully disclose behavioral scope.

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 compact and well-structured, with a lead sentence stating the purpose, followed by Args and Returns sections. Every sentence earns its place; no redundant or filler content. The key information is front-loaded.

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?

The tool is simple (one parameter) and has an output schema (not shown) that likely details the return structure. The description covers the purpose and return basics, but lacks any mention of usage context, error handling, or comparison to sibling tools. For a security-related inspection tool, agents might need to know when to prefer this over sanitization, which is missing.

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 input schema only names the parameter 'image_path' with type string, offering no description. The tool description adds meaning by stating 'Absolute or relative path to the image file,' clarifying the expected format and scope. Since schema coverage is 0%, this compensation is essential and well-executed.

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 clearly states the tool's function: 'Inspects an image for AI detection risks, C2PA manifests, and EXIF footprints.' This is a specific verb and resource with enumerated focus areas, making it easy to understand what it does and to differentiate from sibling tools like strip_metadata_only or anti_ai_sanitize, which are modification tools.

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 no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where inspection is preferred over sanitization, nor does it indicate when not to use it. The sibling tools exist for related tasks, but the description gives no routing hints.

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