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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds a genuinely useful trait beyond structured data: a 12-hour cache, which informs freshness expectations. It stays quiet on pagination/result limits, but that is a minor gap.

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?

Two tight sentences, front-loaded with the outcome, then the usage condition, then the caching caveat. No filler or redundancy.

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 an output schema present, return values needn't be explained, and annotations cover safety. The description supplies purpose, sequencing, scope, and cache behavior, leaving only sibling differentiation against get_ranked_keywords unaddressed.

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 100% with well-documented params (domain, projectId, languageCode, locationCode), so the schema carries the heavy lifting. The description hints at domain scope but adds no syntax or default detail beyond what the schema already provides, matching the baseline 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?

States a specific verb and resource ('Returns the organic keywords a domain ranks for') and names the returned fields (position, available metrics). However, it never distinguishes this from the very similar sibling get_ranked_keywords, so an agent cannot tell the two apart from the descriptions alone.

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?

Gives clear sequencing guidance ('Use after get_domain_overview') and a scope ('for a competitor or reference domain'), which tells the agent when this is the right call. It does not name an explicit alternative for the near-identical ranked-keywords use case, so it stops short of full when-not guidance.

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