bing_crawl_stats

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not what statistics are returned, the time window, whether the site must be verified (the schema hints at it but the description does not), or any rate/permission constraints. For a no-annotation tool this is a complete gap.

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?

One short sentence is technically economical, but this is under-specification rather than conciseness; there is no front-loaded verb or scope to orient the agent. Nearly all decision-relevant information is absent.

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 and no annotations exist, so the description is the only source of context, and it supplies none about what "crawl statistics" contains or how it differs from bing_crawl_issues. An agent could not confidently choose this tool over its siblings.

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 there is a single required parameter (siteUrl) whose schema text explains it is the exact URL of a verified property. Per the high-coverage baseline, the schema does the heavy lifting, so the description adds nothing but does not need to.

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?

"Estadísticas de rastreo de Bing" is essentially a Spanish restatement of the tool name bing_crawl_stats; it names the resource but no specific verb, scope, or metric. It gives no way to distinguish it from close siblings such as bing_crawl_issues or bing_top_queries.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, despite a crowded Bing/GSC sibling set. The only usable signal is the tool name itself, so the agent must infer usage entirely.

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