document_page_validate

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

readOnlyHint=true already tells the agent this is a safe inspection. The description adds genuinely useful method context ('using native visual bounds'), clarifying the basis of the geometric checks. It stops short of describing what a failed validation yields or whether it mutates anything, but with annotations carrying the safety profile a 3 is fair.

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?

A single dense sentence that front-loads the verb and enumerates the checks in order of importance. No filler, though the phrase is packed enough that it verges on hard 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?

An output schema exists, so return values need no explanation, and readOnlyHint covers safety. The gap is the unconveyed expectedRevision contract and any behavior on revision mismatch, which matter for correct invocation of a 3-required-parameter tool.

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 0% across three required parameters, so the schema contributes no semantics. The description explains none of them, and notably ignores expectedRevision, whose 64-hex pattern strongly implies an optimistic-concurrency/revision-match contract that the agent cannot learn from anywhere else.

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 ('Validates') plus three concrete checks: page overlap, empty pages, and objects outside every page. An agent knows exactly what condition set is tested. It does not, however, distinguish itself from the closely related sibling document_preflight, which likely performs a similar validation pass.

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 on when to run this versus document_preflight, document_inspect, or document_pages, and no mention of prerequisites such as needing a workspace-bound path. Usage must be inferred entirely from the name and description.

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