veraPDF by pagespool

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

Beyond readOnlyHint and openWorldHint, the description discloses important behavioral limits: only machine-checkable PDF/UA rules are covered, human review remains necessary, inputs are capped at 4 MB decoded, specific failure codes exist (not_a_pdf, engine_unavailable), and each call costs 10 credits.

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 front-loaded with purpose, then scope caveat, inputs, outputs/errors, and cost. Most sentences earn their place, though the detailed return-field enumeration overlaps with the output schema and makes it denser than strictly necessary.

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 read-only validator with an output schema, the definition is complete: it explains the standard, the scope of automated checking, input alternatives and size limit, profile choice, key return fields, error cases, and credit cost.

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 schema already explains pdf_base64, file, and profile. The description restates the two input paths and the ua1/ua2 choice but adds little format or selection meaning beyond what the schema already provides.

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 states a specific verb and resource: check whether a PDF is accessible under PDF/UA, the ISO standard for accessible PDF. This clearly distinguishes it from the sibling validate_pdfa, which concerns PDF/A rather than accessibility, without needing to name it.

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?

It clearly frames the tool as a PDF/UA accessibility check and notes that human review is still needed for semantic issues like alt text quality and reading order. It does not explicitly route between this and validate_pdfa, but the standards differ enough that the intended use is evident.

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

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

Annotations only declare read-only and open-world behavior; the description goes well beyond by disclosing the 2-credit cost, the 4 MB decoded size ceiling, and the specific failure modes (`not_a_pdf`, `engine_unavailable`). That tells an agent the real operational constraints of an external-engine call.

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?

Front-loads the purpose in one sentence, then organizes inputs, outputs, errors, and cost into short blocks with no filler. The enumerated return fields are somewhat verbose given an output schema exists, keeping it just short of a 5.

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 read-only validation call with a nested file object and an output schema, the description covers input alternatives, limits, cost, error codes, and where to go for a fuller report. Nothing an agent needs to invoke it correctly is missing.

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%, and the description mostly restates it — the 4 MB limit on `pdf_base64` and the meaning of `profile` are already in the schema, including the `auto` fallback behavior. It confirms the intended one-of input pairing but adds no new semantics, so the baseline 3 applies.

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?

States a specific verb (check conformance), resource (a PDF), and the exact standard and engine (PDF/A ISO archiving standard, veraPDF). This is far more precise than the sibling check_pdf_accessibility, which targets a different property of the same file type.

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?

Explains the two mutually exclusive input routes (inline base64 vs. a download link) and redirects to the REST API when a full JSON/XML/HTML report is needed. It never explicitly says when to prefer this over check_pdf_accessibility, so sibling routing is left to inference.

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