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

Beyond the annotations, the description discloses important behavior: the tool costs USD 0.003 per call, payment is via x402 with USDC on Base, and failed calls are not charged. It also states the 10 MB limit and supported file formats, which are material operational details not covered by the annotations.

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 well-structured sentence that front-loads the main action, supported formats, size limit, pricing, and failure policy. Every clause adds useful information without repetition.

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 two-parameter tool with no output schema, the description covers the input constraints, cost model, and conversion target adequately. It does not describe the exact return payload, but the tool's purpose and constraints are sufficiently clear for invocation.

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 input schema already explains filename and file_base64. The description adds no parameter-level detail beyond restating that an uploaded document is converted, so the baseline score is appropriate.

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 states a specific verb and resource: convert an uploaded document to Markdown. It also enumerates supported document types and the 10 MB limit, which clearly separates it from the URL-oriented sibling url_to_markdown by focusing on uploaded files.

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?

Usage is implied by the phrase 'uploaded document,' but the description does not explicitly state when to use this instead of alternatives such as url_to_markdown. It gives practical constraints like size and supported formats, but no direct routing guidance.

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