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

Annotations already establish read-only, closed-world, non-destructive behavior. The description adds concrete thresholds (data repetition <= 1/5, >= 3 searches, <= 1 page/day) and cost ('Free'), but does not explain what the check returns or how failures are reported.

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 criteria are front-loaded after a clear trigger clause, and the rationale/cost sentence is compact. The phrasing is dense but not padded.

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?

No output schema exists, so the description should ideally say what a caller gets back; instead it only lists the pass criteria. It is sufficient to understand the check's intent but incomplete for interpreting results.

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 low (33%), with only pattern described in the schema. The description conveys what dataFields are used for (uniqueness threshold) and what pattern represents (search demand), but it does not explain the pages array shape or how dataFields map to page fields.

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 names the resource (a set of pages from one template) and the three validation criteria, making clear this is a pre-ship check. It does not explicitly contrast with sibling checkers like check_content or landing_check.

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 gives a clear trigger: use before a set of pages from one template ships. No exclusions or named alternatives are provided, so it stops short of full when-to-use guidance.

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