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

No annotations exist, so the description carries the full burden. It goes beyond a simple action by disclosing the return payload structure (organic results with rank, domain, title; PAA; related searches; non-organic blocks) and explicitly handling the edge case where empty arrays are a valid finding, not an error. It also states 'Public data' which implies no auth requirements.

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?

Two sentences deliver a wealth of information without fluff. The first sentence front-loads the action and enumerates outputs; the second covers access and edge-case behavior. Every clause earns its place.

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?

With one required parameter and no output schema, the description fully compensates by detailing what the tool returns, including specific components (organic, PAA, related, blocks) and the empty-array behavior. It's sufficient for an agent to set expectations and interpret results correctly.

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 already provides 100% coverage for the single keyword parameter, including an example. The description doesn't add extra syntax or semantics for the parameter itself, but given the high schema coverage, the baseline of 3 is appropriate. No further detail is necessary.

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 a specific verb and resource: 'Check the live Google search results for any keyword'. It then enumerates the exact outputs (top 10 organic results, People Also Ask, related searches, non-organic blocks) and the purpose (detecting AI Overview or local pack slots). This clearly distinguishes it from siblings like check_aeo_record, which suggests a different record-based operation.

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 provides implied usage context: 'any keyword' indicates broad applicability, and 'Public data, no catalog entry required' signals that this tool is a lightweight, on-demand check without prerequisites. It doesn't explicitly name alternative tools or exclusion criteria, but the context is clear enough for an agent to know when this tool fits.

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