Analyze Bing performance trends over time. Track clicks, impressions, CTR, and position with daily or weekly granularity to identify changes in site performance.
Advanced time series analysis for Bing performance data
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site | |
| days | No | Number of days (default 60) | |
| granularity | No | Data granularity | |
| metrics | No | Metrics to analyze |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits like read-only nature or required permissions. It merely states 'advanced time series analysis,' implying it retrieves data, but this is speculative and insufficient for an agent.
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 a single sentence, which is concise, but the word 'advanced' is subjective and adds little value. It could be restructured to be more informative while remaining brief.
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 4 parameters, no output schema, and many sibling tools, the description is too scant. It fails to explain return values, level of detail, or how it differs from related tools like analytics_time_series.
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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what the schema provides for parameters like 'siteUrl,' 'days,' or 'metrics.' No further parameter details are offered.
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 'Advanced time series analysis for Bing performance data' clearly indicates the tool is for time series analysis, distinguishing it from other analytics tools. However, it lacks specificity on the exact resource being analyzed (e.g., clicks, impressions) and could be more precise.
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_analytics_trends or analytics_time_series. The description does not include any context about use cases or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.