image-to-markdown

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the conversion includes metadata and description, which adds some context about output behavior. However, it lacks details on error handling, performance characteristics, or any side effects, leaving gaps in understanding how the tool behaves beyond the basic operation.

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, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core purpose and includes a brief mention of output features, making it easy to understand quickly. Every part of the sentence contributes to clarifying the tool's role.

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?

Given the tool's moderate complexity (conversion with metadata) and lack of annotations and output schema, the description is minimally adequate. It covers the basic operation and hints at output content but does not fully address behavioral aspects or provide complete context for effective use. The description meets the minimum viable standard but has clear gaps in usage and transparency.

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 has 100% description coverage, clearly documenting the single parameter 'filepath' as the absolute path of the image file. The description does not add any additional meaning beyond what the schema provides, such as supported image formats or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 purpose: converting an image to markdown, including metadata and description. It specifies the verb 'convert' and the resource 'image', distinguishing it from sibling tools that handle other file types like audio, PDF, or webpage. However, it does not explicitly differentiate from siblings beyond the resource type, as all sibling tools involve conversion to markdown.

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 does not mention prerequisites, such as the image file needing to be accessible or in a specific format, or when to choose this over other markdown conversion tools for different content types. Usage is implied by the tool name but not explicitly stated.

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