Check which recent days have final data and which are still changing for daily and hourly Google Search Console metrics.
Which recent days are final and which are still changing, for daily and hourly data.
| Name | Required | Description | Default |
|---|---|---|---|
| site_url | Yes | ||
| search_type | No | web |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds some domain semantics about final versus changing recent days, but it does not disclose auth requirements, rate limits, or other behavioral constraints beyond the annotations.
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 front-loaded sentence with no wasted words. It is appropriately sized, though its brevity contributes to the gaps in parameter and usage guidance.
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?
An output schema exists, so return values need not be described, and annotations cover safety. However, with 0% schema coverage, the description should compensate for parameter meaning and usage guidance, which it does not. An agent lacks enough context to invoke the tool confidently.
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 0% for two parameters: required site_url and optional search_type with default 'web'. The description does not explain what either parameter means or what values are expected. The phrase 'daily and hourly data' does not clearly map to search_type or compensate for the missing schema documentation.
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 states a clear query purpose: identifying which recent days are final versus still changing, for daily and hourly data. It is understandable without opening the schema, but it does not distinguish this tool from related siblings such as history_status or performance_overview.
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 explicit guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The description implies a freshness-check use case but leaves the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.