pdf_info

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

Annotations already declare readOnlyHint=true. Description adds meaningful context: 'Reads the file on this machine; nothing leaves it.' This clarifies data locality and privacy, which is important for agents operating on local files. No contradiction with 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?

Two sentences, no waste. Front-loaded with purpose, then usage guidance, then behavioral note. Every sentence is essential.

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?

Clearly states outputs: page count, per-page size, and text-layer presence. No output schema, but description sufficiently covers expected information. Minor gap: does not specify output format (e.g., JSON structure), but given the tool's simplicity, it is nearly complete.

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 has 0% description coverage; the single 'path' parameter has only type and title. Description does not elaborate on path format, allowed values, or how to specify the file. It only implies the file is local. Given the gap, description should compensate but does not.

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 uses specific verb 'Inventory' and identifies resource 'PDF'. It clearly states what metadata is extracted (page count, per-page size, text vs. scan/drawing) and directly differentiates from sibling tools by mentioning pdf_extract_text, ocr_pdf, and pdf_pages_to_images.

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?

Explicitly guides when to use this tool: as a pre-read inventory step. Names three sibling tools and the decision criteria (text layer vs. scans vs. drawings), providing clear context for the agent to choose the correct subsequent tool.

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