image_metadata

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It clearly indicates a read-only operation via 'extract' and details what the tool returns, plus the path constraint that the file must be under home directory. However, it does not mention error handling, file type limitations, or permission requirements.

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 concise, opening with a direct purpose statement followed by a focused list of return categories. The explicit Args section adds necessary detail without redundancy, and every sentence contributes to understanding.

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?

For a single-parameter tool with an output schema, the description provides sufficient context: it states the purpose, lists the returned metadata types, and explains the path constraint. Despite lacking explicit usage guidance, the core operation is fully specified for the agent to invoke correctly.

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 provides only a type-less 'path' property with no description. The description compensates fully by defining 'path' as 'Absolute path to the image file' and adding the additional constraint that it must be under the home directory, giving the agent complete parameter semantics.

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 'Extract full metadata from an image,' which clearly states the verb and resource. It then enumerates specific metadata categories (file info, image properties, EXIF), distinguishing it from sibling tools like ocr_image and extract_text that handle text extraction.

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 does not explicitly guide when to use this tool versus alternatives. While it is clear the tool is for metadata extraction, it never mentions the text-focused siblings or provides when/when-not guidance, leaving usage to be implied.

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