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 the output includes 'metadata and description,' hinting at what the tool returns, but lacks details on error handling, performance (e.g., processing time), or limitations (e.g., file size constraints). For a tool with no annotations, this is insufficient to fully inform the agent about its 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 a single, efficient sentence: 'Convert an image to markdown, including metadata and description.' It is front-loaded with the core purpose and avoids unnecessary words, making it highly concise and well-structured for quick 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?

Given the tool's moderate complexity (conversion with metadata), no annotations, and no output schema, the description is minimally adequate. It specifies the input (image) and output (markdown with metadata), but lacks details on output structure, error cases, or integration context. This leaves gaps that could hinder effective use by an agent.

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, with the 'filepath' parameter clearly documented as 'Absolute path of the image file to convert.' The description adds no additional parameter semantics beyond this, such as format requirements or examples. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles the heavy lifting.

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: 'Convert an image to markdown, including metadata and description.' It specifies the verb ('convert'), resource ('image'), and output format ('markdown'), distinguishing it from sibling tools like 'audio-to-markdown' or 'pdf-to-markdown' by focusing on images. However, it doesn't explicitly differentiate from similar tools beyond naming, keeping it at a 4 rather than a 5.

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 prerequisites (e.g., file accessibility), exclusions (e.g., unsupported image formats), or comparisons to sibling tools like 'webpage-to-markdown' for different content types. This lack of context leaves the agent to infer usage based on the name alone.

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