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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description earns credit by disclosing the auth mechanism concretely (Bearer nsr_… or x-api-key, plus the endpoint URL), which is real operational context not present in annotations. It stops short of covering rate limits, error behavior, or partial-result cases.

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?

Front-loaded with the core purpose, then the field inventory, then the auth requirement. The dense field enumeration is long but earns its place because there is no output schema to document return values. Slightly overstuffed as a single run-on sentence.

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 usefully compensates by naming the categories of data returned (traffic history, backlinks/DR, revenue grade, AI take, competitors). Auth and endpoint are supplied. Gaps are minor: no mention of response shape, pagination, or failure modes.

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?

Only one parameter and schema description coverage is 100%, with the schema already explaining 'Bare domain, e.g. example.ai' and enforcing a regex pattern. The description adds no additional meaning about the domain argument, so the baseline 3 applies.

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 (fetch everything on one tracked site) and enumerates the exact data domains returned, which makes it trivially distinguishable from list/search siblings like search_sites and top_rising. The scope phrase 'one tracked site' signals single-entity lookup.

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 already have a domain and want the full profile rather than a list. The description states a prerequisite (Pro API key) but never explicitly says when to prefer this over search_sites or how it differs in cost/latency, so guidance stays at the implied level.

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