PDF info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and repeatability are covered. The description adds useful output-oriented context, especially the OCR/text-layer signal and encryption facts, but does not discuss failure behavior, limits, or other operational traits beyond what the schema annotations imply.

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 front-loaded sentence with a colon-delimited list of outputs, making it easy to scan. It is somewhat dense, and the external web-tool link is marginally useful, but there is little wasted language.

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?

With no output schema, the description usefully enumerates the key return facts so an agent knows what information it will receive. Given complete parameter descriptions and read-only annotations, this is largely sufficient, though explicit sibling routing guidance would make it more 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 description coverage is 100%, so the file, password, and textCheck parameters are already well documented in structured form. The description does not add syntax or semantic detail beyond the schema; it mainly describes returned information, so the baseline 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 identifies the resource as a PDF and enumerates the specific facts returned: page count, page sizes, rotation, encryption, version, form fields, title/author, and missing text layers. It implies inspection/planning rather than mutation, but it does not explicitly name or distinguish itself from close siblings such as pdf_metadata_read, pdf_form_fields, pdf_to_text, or ai_ocr.

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 phrase 'for planning the next step' and the note about pages that 'would need OCR' imply appropriate usage contexts. However, it gives no explicit when-to-use guidance, exclusions, or named alternatives, so an agent must infer routing from the output list.

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