get_pdf_metadata

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

Clearly states no extraction, implying read-only behavior, and lists metadata returned. While it doesn't cover all behavioral details (e.g., file existence requirements), it is transparent enough for a simple metadata tool.

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 covering purpose, output, and usage guidelines with zero wasted words; information is front-loaded and clearly structured.

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 output schema exists, the description adequately covers what the tool returns and how to use it in a workflow. Lacks error handling details but is sufficient for its simplicity.

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 only parameter 'file_path' has no schema description (0% coverage), and the description does not add details about valid file types, path format, or access requirements, leaving interpretation to the field name.

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?

Explicitly states it retrieves PDF metadata (page count, file size, document type, table presence) and distinguishes from siblings by clarifying no extraction is performed.

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?

Directs to use this first and lists specific alternatives (convert_pdf, analyze_pdf, extract_structured) based on the need, providing clear decision guidance.

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