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

With no annotations present, the description carries the behavioral disclosure burden. It clearly states pricing (2 credits), free repeats of known-empty lookups, output contents, and the default limit. It does not explicitly mention that this is a read-only lookup, but the phrasing and 'returns' wording make that sufficiently clear.

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 tight and well-ordered: what the tool returns, cost behavior, and output shape in three short statements. No filler, and the most important distinction (keyword-overlap competitors) is front-loaded.

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 covers input/output expectations, the default and maximum limit behavior, and the unusual free-on-empty cost ruleasia; without an output schema, the listed return fields are helpful. It lacks explicit notes on when the call is inappropriate or how country impacts results, but those are minor gaps.

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 fully documents `domain`, `limit`, and `country`, including defaults and constraints, so the description adds little new parameter semantics. The only added value is confirming that `limit` defaults to 50 and does not affect cost, which repeats the schema's own explanation.

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 concrete action: it lists domains competing for the same Google keywords as a target, and specifies top-100 keyword-overlap ranking plus the exact metrics returned (overlap share, average position, total keywords, traffic, ads). This clearly separates it from related tools such as backlink-focused competitor lookups.

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 when to use it ('Domains competing for the same Google keywords') and gives operational details like credit cost and free repeated lookups. However, it does not explicitly contrast it with sibling tools or state when not to use it, so the guidance is contextual rather than exclusionary.

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