pdf_info_reader

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

With no annotations, the description must fully convey behavior. It indicates a read operation but lacks details on error handling, rate limits, or authentication requirements beyond the schema. The reference link is available but not part of the description itself.

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 with concrete examples of output, followed by a concise reference link. Every word adds value; no redundant or fluff content.

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 lack of output schema, the description gives a good overview of return values (pages, metadata, etc.). Input schema is fully described, and complexity is moderate. Sibling tools provide context for differentiation, making the description nearly 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?

Schema coverage is 100%, and each parameter is well-described. The description does not add additional context to parameters beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 retrieves detailed PDF information including pages, metadata, security, and form fields. The verb 'Get' and resource 'PDF document' are specific, and the listed outputs differentiate it from siblings like pdf_to_text or pdf_to_image.

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 usage for obtaining metadata and structure but does not explicitly state when to use this tool versus siblings (e.g., pdf_to_text for text extraction). No when-not or alternative tool names are mentioned, relying on implicit differentiation.

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