Convert PDF to JSON

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral details: it returns a structured JSON with source, total_pages, metadata, and pages array, and explains the output behavior when output_path is set (writes file, returns summary). No contradictions.

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?

Description is concise and well-structured: first paragraph explains purpose and differentiation, second describes parameters, third shows return format and example. No unnecessary words, every sentence contributes.

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 annotations and full schema coverage, the description is nearly complete. It covers return structure, parameter behavior, and usage alternatives. Could mention error cases (e.g., file not found) but not required for basic operation.

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 provides 100% coverage with descriptions. Description adds value: 'path' is clarified as 'The PDF file' and 'output_path' explains the conditional behavior (if set, writes JSON and returns summary). This enriches the schema information.

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 converts a local PDF into structured JSON, enumerating document metadata, page count, and text per page. It distinguishes itself from the sibling tool 'read_file' by specifying the additional capabilities.

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?

Explicit guidance on when to use this tool versus the alternative 'read_file': 'Use read_file for a quick plain-text read; use this when you need page structure, metadata, or a JSON file other tools can consume.' This provides clear context for tool selection.

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