bing_top_pages

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

The description specifies the scope (US traffic) and date range defaults, but lacks details on data freshness, pagination, or what 'top' means (e.g., number of pages). No annotations are provided to compensate.

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 description is concise with a purpose statement and args listing. It is efficient but could be slightly improved by front-loading key details like US traffic scope.

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?

Given the output schema existence, return values are covered, but the description does not clarify usage context among many sibling tools or mention any limitations (e.g., rate limits, authentication). It is minimally complete but leaves gaps.

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?

The description adds meaning to the parameters by specifying expected format (YYYY-MM-DD) and defaults (start_date: 28 days ago, end_date: today), beyond the bare schema with no descriptions.

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 top Bing pages by clicks for US traffic, distinguishing it from sibling tools like bing_top_queries or bing_keywords.

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 is provided on when to use this tool versus siblings such as bing_top_queries or bing_page_query_matrix. No excluding conditions or prerequisites are mentioned.

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