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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds two useful non-annotation facts: the lookup is 'live' (real-time query) and that 0 is a sentinel meaning 'not in top 100' — important since there is no output schema to convey it.

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?

One front-loaded sentence with the resource and scale up front and the edge-case sentinel tucked into a parenthetical. No 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?

With no output schema, the description does cover the return value (position, 0 = not in top 100), which is the most important gap filled. But for a 3-parameter tool it leaves the country dimension and domain/keyword input conventions entirely to a mostly empty schema.

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 only 33% — domain and keyword are bare strings and country is the only documented parameter (sg|us|uk|au|my, default us). The description loosely maps domain and keyword but says nothing about domain format (protocol, subdomain, path), how keyword matching works, or what country does and that it defaults to us.

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?

States a concrete verb+resource (get a domain's live Google organic position for a keyword) and defines the result scale. It does not mention the siblings ai_presence or page_meta, so differentiation must be inferred from the resource names.

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?

Usage is implied: call it when you want a rank for one domain/keyword pair. There is no explicit when-not guidance (e.g., bulk checks, non-Google engines, or the adjacent presence/meta siblings), and nothing about cost or rate limits despite 'live' implying a real-time lookup.

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