convert_pdf_to_markdown

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions a 'one-step workflow' but does not explain whether the operation is synchronous, what side effects occur, or any authentication or rate-limiting requirements. Critical behavioral context is missing.

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 sentence that is front-loaded with the most important information (alias relationship). It is concise and contains no unnecessary words, making it efficient for an agent to parse.

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 is a conversion with four parameters and no output schema, the description is incomplete. It omits crucial context such as how results are returned, error handling, and whether the process is asynchronous. The presence of sibling tools like get_task_status suggests async workflow, but this is not clarified.

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 covers all four parameters with descriptions (100% coverage). The description adds no new parameter-level information beyond what the schema already provides. Thus, the description provides no added value for parameter understanding.

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 explicitly states it is an alias for convert_to_markdown and lists all supported formats. The verb 'convert' and resource 'to markdown' are clear, and it distinguishes itself from siblings by being a direct alias.

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 lacks explicit guidance on when to use this tool versus alternatives. It only states it's an alias, but does not explain when to prefer it over other sibling tools like get_task_status or create_parse_task.

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