doc_pdf_metadata

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

No annotations are provided, so the description carries full burden. It explains the extraction process (parsing /Info dictionary and XMP) but lacks details on error handling, file requirements (e.g., encryption), or return format. Basic transparency is adequate but not comprehensive.

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 extremely concise with two sentences. The first states the core function, the second adds technical details and a use case. Every sentence is informative with no redundancy.

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 simple tool (one parameter, no output schema), the description covers basic functionality and a use case. However, it does not specify the output format (e.g., returns a dictionary) or mention potential edge cases (e.g., missing metadata). This leaves some gaps for an agent to understand what the tool returns.

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 coverage is 100% with a clear description of the file_path parameter. The description adds the context that the tool extracts metadata, but does not provide additional details about parameter format, validation, or allowed values beyond the schema.

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 'PDF metadata extraction' with specific details about parsing /Info dictionary and XMP metadata. This distinguishes it from sibling tools like doc_xml_metadata (for XML files) and doc_pdf_hidden (for hidden content).

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 a use case ('forensic attribution and document provenance analysis') but does not explicitly guide when to use this tool over alternatives or specify exclusions. No comparison with sibling tools is made.

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