pdf_info_reader

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

With no annotations provided, the description must fully convey behavioral traits. The use of 'Get' implies a read-only, non-destructive operation, and the list of returned information gives some insight. However, it does not disclose potential side effects, authentication requirements beyond the API key, rate limits, or error behavior. The description is transparent about output scope but not about operational 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 sentence that front-loads the primary purpose and lists key outputs. The reference link is auxiliary and not clutter. Every word contributes to understanding the tool's function, making it highly concise and well-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?

This is a relatively simple read tool with well-described parameters and no output schema. The description provides a clear inventory of what the tool returns, which is sufficient for an agent to select and invoke it. The only missing context is the return format (e.g., JSON structure) and whether any authentication beyond the API key is needed, but these are minor given the tool's 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 input schema has 100% description coverage for all 5 parameters, so the schema already documents each parameter's purpose. The description adds no extra semantic value for parameters. This meets the baseline but does not exceed it, as the description does not clarify parameter relationships or provide examples beyond what the schema gives.

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 tool's purpose: to get detailed information about a PDF document, listing specific data types (pages, metadata, security, form fields). This is specific enough to understand the resource and action. However, it does not explicitly differentiate from sibling tools like read_pdf_forms_info, which focuses on form fields specifically.

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 no guidance on when to use this tool versus alternatives. It does not mention that read_pdf_forms_info exists for form-specific extraction, nor does it suggest any preconditions or use cases. The reference link might provide context, but the description itself lacks usage direction.

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