convert_document

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

Discloses automatic USDC payment via x402, cost ceiling via max_usdc, and conditional return types. No annotations provided, but description compensates well. Could mention error/failure modes.

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?

Structured with intro and Args list. Somewhat verbose due to bilingual text, but each sentence adds value. Could be tighter by removing redundancy.

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?

Covers conversion, payment, cost control, output formats. No output schema but describes returns. Missing edge cases (e.g., errors, unsupported formats) but sufficient for typical use.

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?

All three parameters explained in plain language (Korean): file_path, max_usdc, poll_seconds. Adds meaning beyond schema, including defaults and purpose.

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?

Description clearly states verb 'converts' and resource 'document to Markdown', with specific behaviors (payment, conditional output). Distinguishes from sibling 'estimate_conversion' by being the execution tool.

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?

Provides implicit guidance: use when you want to convert with payment, reject if over max. Describes how output differs based on images. Lacks explicit when-not-to-use or direct sibling comparison.

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