pdf-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 operation (implying mutation of format), specifies constraints for 'filepath' (must exist on server), and mentions a prerequisite for local files (upload first). However, it lacks details on rate limits, error handling, or output format specifics.

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 in the first sentence, followed by specific usage guidelines. Every sentence adds value without redundancy, making it efficient 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 operation with two parameters) and no annotations or output schema, the description does a good job covering purpose, usage, and constraints. It could be more complete by detailing the output format or error cases, but it provides sufficient context for basic 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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds some context by explaining the use cases for 'url' (online PDFs) and 'filepath' (server-side files), but does not provide additional syntax or format details beyond what the schema states. This meets the baseline for high schema coverage.

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 verb 'convert' and the resource 'PDF file to markdown', making the purpose specific and unambiguous. It distinguishes itself from sibling tools like 'docx-to-markdown' or 'image-to-markdown' by specifying PDF as the input format.

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 PDFs and 'filepath' only if the file exists on the server. It also mentions an alternative action ('upload them first via /upload endpoint') for local files, which helps differentiate from sibling tools like 'upload-file-for-conversion'.

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