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

Annotations already establish readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results are summed over the date window, sorted by clicks by default, and the `page` flag flips the tool into a query-level view.

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, zero waste, and the primary behavior (the page list and its metrics) is front-loaded before the alternate `page` mode.

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, the description helpfully enumerates the returned fields (clicks, impressions, CTR, average position) and the default sort, and the schema covers dates, site selection and row limits. Pagination beyond `limit` is not addressed, a minor gap.

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%, so every parameter is already documented in the schema, giving a baseline of 3. The description reinforces the meaning of `page` and the sort order but adds no syntax or format detail beyond what the schema provides.

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 resource (the site's pages receiving Bing search traffic), the metrics attached (clicks, impressions, CTR, average position), the aggregation (summed over the window) and the ordering (sorted by clicks). It also explicitly describes the alternate mode when `page` is passed, which cleanly separates it from 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?

Gives clear context for the default call and explicitly routes to a different result set via `page` ('instead see which searches that one page shows up for'). It does not name the sibling tool bing_top_queries as the alternative, so the routing is implicit rather than explicit.

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