extract_markdown_v1_documents_to_markdown_post

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

With no annotations provided, the description carries the behavioral burden. It discloses the conversion behavior, claims spatial awareness, warns about hallucinations, and mentions cost/payment. However, it does not describe the output format, success/failure behavior, or side effects (e.g., whether it consumes credits even on failure). The description gives a good overview but omits some behavioral specifics that an agent might need.

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 somewhat verbose, with an imperative system-instruction tone, all-caps emphasis, and repetition of the conversion concept. It could be tightened to two sentences without losing essential information. While it is front-loaded with the directive and includes cost information, it does not earn every sentence fully.

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 absence of an output schema, the description should explain what the tool returns (e.g., a Markdown string or URL) and clarify the requirement that at least one input parameter must be supplied. It also leaves the 'images' discrepancy unresolved. These omissions make the tool less predictable for an 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 input schema has 100% description coverage for both parameters, but the description adds no extra semantic detail. Worse, it mentions 'PDFs or images' while the schema only accepts PDF URLs and base64 strings, creating confusion about image support. The description also fails to note that at least one parameter must be provided, even though neither is marked required. This is a missed opportunity and a slight misdirection.

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 PDFs or images into Markdown. It uses a specific verb ('convert') and a specific resource ('PDFs or images'), and it distinguishes itself from sibling tools like extract_invoice and extract_resume, which are for specific document types, while this one is a general conversion tool. The purpose is unambiguous and actionable.

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 usage guidance: use this tool before attempting any reasoning or extraction, and do not rely on standard text extraction libraries. It also mentions cost and payment recovery. However, it does not contrast this tool with other document extraction siblings (e.g., extract_invoice), so it lacks 'when not to use' relative to those alternatives. Still, the contextual guidance is strong.

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