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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds genuinely useful context the annotations do not: that the call consumes SEO add-on credits and requires the SEO Intelligence add-on to be active, plus that it queries external engines. However, it never explains why a measurement tool is marked destructive, leaving a real ambiguity.

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?

Three short sentences that front-load the core purpose, which is appropriate. But the mid-sentence line break hurts readability and the trailing 'top up → Add-ons' fragment is cryptic rather than informative.

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?

An output schema exists, so return values need not be described. Still, for a 4-parameter, credit-consuming, destructive-flagged tool, the description omits all non-brand parameter semantics and does not explain the destructive/credit-spending behavior concretely enough for an agent to act safely.

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% across 4 parameters, so the description carries the full burden and largely fails it. Only 'brand' is implied by the text; refresh, language (default 'tr') and location are never mentioned, so the agent has no guidance on locale scoping or cache-busting behavior.

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+resource: tracking how often a brand is MENTIONED in AI answer engines (Google AI Overviews, ChatGPT) with an AI search volume estimate, and labels the domain as GEO. This is clear on its own, but it does not distinguish itself from close siblings such as seo_geo_tracker, seo_ai_overview or seo_brand_monitor, so an agent cannot tell from the text which one to call.

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 only implied through the add-on framing ('SEO Intelligence add-on', 'Costs SEO add-on credits; top up → Add-ons'), which tells the agent a prerequisite exists but not when this tool is preferable to the many adjacent SEO/GEO tools. No alternatives or exclusions are named.

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