get_pdf_info

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

With no annotations provided, the description fails to disclose behavioral traits such as whether the tool requires a local file, performs network access, or has latency. The description only restates the purpose, offering no insight into side effects or requirements beyond the input schema.

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, concise sentence with no extraneous words. It is front-loaded with the essential action and resource, making it efficient for an agent to parse.

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?

Despite having an output schema (not shown), the description does not explain what metadata or basic information is returned. For a tool that returns data, this is a significant gap; the agent cannot predict the structure or fields. Additionally, the parameter description could be enhanced with examples or constraints.

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 input schema has 100% description coverage for the single parameter file_path, which already states 'Path to the PDF file.' The description adds no additional semantics or constraints (e.g., supported file extensions, absolute vs relative paths). Baseline score of 3 is appropriate given schema coverage.

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 resource (metadata and basic information about a PDF file). It distinguishes from sibling tools like get_pdf_structure and read_pdf_text, which handle structural or textual content. However, it could be more specific about what metadata is included (e.g., page count, file size, author).

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?

No guidance is provided on when to use this tool versus its siblings. There are no explicit statements about prerequisites, such as file availability or format support, nor any comparison to alternatives like search_pdf_text. The usage context is only implied.

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