estimate_pages

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

Discloses it's a non-downloading, fast preview, which suggests read-only behavior. However, lacks explicit statements about side effects, permissions, or output format beyond what the output schema might convey.

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?

Two sentences, 12 words, no fluff. Concise but could add a brief parameter explanation without losing brevity.

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 annotations and 0% parameter coverage, the description is too sparse. Does not mention the output type or behavior of optional parameters, leaving gaps for safe usage.

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%, yet the description only implicitly references config_path. Does not explain max_discovery or unlimited, leaving the agent without guidance on their meaning.

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?

Description clearly states the tool estimates page count from a config, and explicitly notes it's a fast preview without downloading content, distinguishing it from scraping siblings.

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?

Implies usage for quick previews, but does not explicitly state when to use vs. alternatives like scrape_* tools, nor provide when-not-to-use conditions.

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