search_console_data

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

Annotations declare readOnlyHint=true, which is consistent with 'Query.' The description adds that a connected GSC source is required, how to obtain IDs, and specific time ranges for certain endpoints (e.g., 'last 3 months' for top_pages, 'last 2 months' for complete_data).

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 tool summary is one sentence, followed by a compact prerequisites line, then a structured Args block with consistent formatting. No filler.

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 exists, yet the description doesn't describe the return format or any pagination/limitations. It also omits 'config.' While the endpoint list gives some idea of output data, it's not fully complete for a tool with this complexity.

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 schema has 0% coverage, but the description explains project_id ('Your project UUID'), account_id ('from list_connections, e.g. sc-domain:example.com'), and endpoint (listing each enum value with meaning). However, the 'config' parameter is completely ignored in the description.

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 opens with 'Query your Google Search Console data — keywords, pages, clicks, impressions, and rankings,' providing a clear verb and resource. However, it doesn't explicitly distinguish itself from sibling tool 'top_pages,' which may have overlapping functionality.

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?

It states a clear prerequisite ('Requires a connected GSC data source') and provides a specific workflow ('Call list_projects() then list_connections()...'), but it doesn't mention alternative tools or when not to use it.

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