get_pdf_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It implicitly indicates a read-only operation by focusing on metadata, but does not explicitly state that no content is extracted or that the file is not modified. This is adequate for a simple metadata getter, but lacks explicit safety or return-format details.

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, focused sentence that opens with the verb and resource, mentions the key metadata fields, and contains no redundant information. It is concise and well-structured for the tool's simplicity.

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?

For a simple tool with one parameter, full schema coverage, and no output schema, the description adequately conveys the purpose and hints at the return content via examples (title, author, pages). It could explicitly state what is returned, but the examples and clear scope make it reasonably 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?

The single parameter file_path has a full schema description, so schema coverage is 100%. The tool description adds no extra meaning beyond what the schema already provides, such as path format or constraints, so it stays at the baseline.

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 verb 'Get' and the resource 'metadata information from a PDF file', with examples of the metadata returned. It is clearly distinct from sibling tools like read_pdf and read_pages, which handle content extraction, making the purpose unmistakable.

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 implies the tool should be used when metadata is needed, but provides no explicit guidance on when to use it versus alternatives. There are no stated exclusions or references to sibling tools, so the usage context is implied rather than explicit.

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