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

With no annotations, the description carries the full burden of behavioral disclosure. It communicates the content of the output (keywords, traffic, positions) but does not state whether this is a read-only analysis, whether it requires authentication, any rate limits, or limitations such as data freshness or accuracy. It is a minimal statement of contents, not deeper behavioral context.

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 a single, front-loaded line that efficiently conveys the tool's purpose by listing the key data components. It is not bloated, but it does omit any contextual or usage information, making it concise but not comprehensive.

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 the absence of an output schema and annotations, the description is under-specified. It lists high-level categories but does not explain the output structure, data granularity, time range, or how it differs from more specific sibling tools. For a tool with two simple parameters, it is still a thin description.

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 input schema already provides descriptions for both parameters (domain and country), covering 100% of the schema. The description adds no additional semantic meaning beyond what the schema states, so it remains at the baseline of 3.

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 identifies the tool as providing a domain-level SEO overview, listing three specific data categories (organic keywords, traffic estimate, position distribution). It distinguishes itself from sibling tools by its broad scope, though it lacks an explicit verb like 'get' or 'retrieve'. It is not a tautology and gives concrete information.

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 offers no guidance on when to use this tool versus sibling tools like keyword_research, rank_tracker, or check_ranking. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer context only from the name and list.

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