get_crawl_stats

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

No annotations exist, so the description carries full burden. It indicates a read operation but fails to disclose prerequisites (e.g., site must be crawled), authentication needs, or potential costs. The brevity leaves the agent uninformed about important behavioral aspects.

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?

Information is front-loaded in a single sentence, which is efficient. However, it is too terse, omitting critical details that could be added without significant length. The score reflects that conciseness comes at the cost of completeness.

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 and low complexity (1 param, no nested objects), the description could have included expected return format or an example. The tool is one of many stat tools; lacking context on what distinguishes this output (e.g., aggregated vs. per-page) reduces its completeness.

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 has 0% description coverage; the description does not mention the site_url parameter at all. It adds no meaning beyond what the schema already provides (the parameter is required and string type). The agent gains no extra guidance on how to specify the site URL.

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 states the tool retrieves crawl statistics, listing three specific metrics (crawled pages, errors, blocked). The verb 'Get' and resource 'crawl statistics' with explicit sub-categories distinguishes it from sibling tools like get_crawl_issues (issues) or get_page_stats (page-level stats).

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 use this tool versus alternatives. With 15 sibling tools including several stat-related ones, the description should clarify that this is for high-level crawl stats vs. more specific metrics (e.g., get_rank_and_traffic_stats). No when-not-to-use or context provided.

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