seo_domain_overview

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that results include organic traffic, keyword count, and visibility, but does not discuss error behavior, rate limits, or data freshness. No contradiction exists between description and 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 concise: a single-sentence summary followed by an Args block. It is front-loaded with the tool's purpose and contains no redundant or filler text.

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?

The description is adequate for basic invocation, naming key output metrics and required parameters. However, with no output schema and an unexplained 'config' parameter, it is not fully complete for an agent to confidently predict all behaviors and outcomes.

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%, so the description carries the burden. It explains 'domain' with an example and 'country' with a default, but the 'config' parameter is completely undocumented, leaving a gap in parameter understanding.

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 it 'Get comprehensive SEO overview for a domain including organic traffic, keywords count, and visibility,' combining a specific verb with a resource and the expected output fields. This distinguishes it from sibling SEO tools like keyword_research or backlink_analysis.

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 implies usage when you need a high-level domain overview, but it does not explicitly state when to prefer this over alternatives or mention exclusions. Sibling tools cover related but different scopes, yet no direct comparison is provided.

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