image-to-markdown

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the tool performs a conversion (implying mutation/processing), specifies input constraints (online vs. server files), and references an upload prerequisite. However, it doesn't mention potential limitations like rate limits, error conditions, or output format details.

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 specific usage rules in two concise sentences. Every sentence earns its place by providing essential information without redundancy, making it highly efficient and well-structured.

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 no annotations, no output schema, and a simple input schema, the description does well by covering purpose, usage guidelines, and behavioral context. However, it lacks details on the output (e.g., markdown structure, metadata format) and potential errors, which could be helpful for a conversion tool with no structured output documentation.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context by explaining the semantic choice between 'url' and 'filepath' (online vs. server files) and the prerequisite for local files, which enhances understanding beyond the schema's technical descriptions. It doesn't provide additional syntax details, but the guidance is valuable.

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 specific action ('Convert an image to markdown') and resource ('image'), distinguishing it from sibling tools like 'audio-to-markdown' or 'pdf-to-markdown' which handle different file types. It also specifies the output includes 'metadata and description', adding precision beyond just conversion.

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 explicit guidance on when to use each parameter ('url' for online images, 'filepath' only if the file exists on the server) and includes an alternative action ('upload them first via /upload endpoint' for local files). This clearly differentiates usage scenarios and references another tool.

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