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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds meaningful context beyond that: it is a 'snapshot' of 'latest' data, both extras default to off, and the 'moves' are explicitly 'scored against you' with a stated relevance frame ('your brand, keywords you both rank for, real gaps'). Missing only freshness/refresh cadence and any cost or plan limitations.

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 sentences, well front-loaded: the core snapshot and its metric list come first, the optional enrichments second. Dense but every clause carries information; the second sentence is long with nested parentheticals, which slightly reduces scannability.

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 annotations covering the safety profile and an output schema covering return structure, the description only needs to convey scope, subjects, and optional enrichments — all present, including the useful qualifier that scope is limited to competitors already being tracked. Nothing an agent needs to call it correctly is absent.

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%, so a 3 is the baseline. The description earns a point above that by explaining the intent of each flag at a conceptual level — keywords are 'top organic' by traffic, and moves are 'scored against you' around brand/both-rank/gap keywords — which helps an agent decide whether to enable them rather than just knowing their type.

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 uses a specific verb ('Get') and a well-scoped resource ('latest SEO snapshot for your product and each competitor'), then enumerates the exact metrics returned (domain rating, organic keywords, traffic, backlinks, referring domains, top-3/top-10 counts). This is unambiguous and non-overlapping with siblings like pricing changes or reviews, but it never names or differentiates itself from those siblings explicitly.

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: an agent can infer 'use this for SEO comparison' from the content, and the two optional flags are explained in terms of what they add. There is no explicit when-to-use vs. when-not, no mention of prerequisites (e.g. competitors must already be tracked, though 'each competitor you track' hints at it), and no routing to the battlecard or feature-gap siblings.

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