Domain SEO overview

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

The description adds significant context beyond annotations: it costs credits, cached results are free, and repeated queries within a week hit the cache. This discloses consumption behavior and non-obvious constraints. However, it does not explicitly state whether the operation is read-only, and annotations show readOnlyHint=false, which could be ambiguous, but nothing contradicts.

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 two sentences, front-loaded with the core output, then usage, cost, and alternative. Every sentence adds value with no redundancy or 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?

For a tool with a single parameter and no output schema, the description fully covers purpose, key alternatives, and cost behavior. It is complete and self-sufficient for an agent to decide when and how to invoke it.

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 full coverage for the single 'domain' parameter with an example. The description reinforces 'ANY domain' and 'competitor', adding slight context but no new technical syntax or format details. Baseline 3 is appropriate.

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 what the tool does: provides estimated organic traffic, keyword count, and top keywords for any domain. It explicitly positions it for sizing up competitors and distinguishes it from gsc_* tools for the user's own site.

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?

Explicit guidance is provided: use it to size up a competitor the user mentions, and prefer gsc_* tools for the user's own site. It also mentions cost implications, which helps the agent decide when to use it.

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