get_search_analytics

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

With no annotations, the description carries the full burden. It discloses many behavioral aspects: parameter defaults (e.g., start_date defaults to 30 days ago), pagination via start_row, and token efficiency for summary_only. However, it omits details on authentication, rate limits, or error handling, preventing a 5.

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 well-structured with an Args list and Returns section. It is slightly verbose due to parameter enumeration, but every sentence provides value. It is front-loaded with the main purpose and organized logically.

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 8 parameters, no output schema, and no annotations, the description covers the essentials: return format, pagination, and filter examples. It could mention related tools (e.g., list_available_dimensions) for dimension values, but it remains complete enough for most scenarios.

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 0%, but the description compensates fully by explaining each of the 8 parameters, including types, defaults, and an example for filters. This adds substantial meaning beyond the bare schema, making it highly useful for correct invocation.

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 'Retrieve Google Search Console search analytics data,' using a specific verb and resource. This distinguishes it from sibling tools like list_gsc_sites and get_sitemaps, which focus on site management or sitemaps.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or when not to use it. It implies usage through parameter explanations but lacks direct guidance, so it earns a 3.

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