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

The description presents a read-only data retrieval endpoint ('provide you with historical backlinks data'), but annotations declare readOnlyHint=false and destructiveHint=true. This is a direct contradiction, and the description adds no behavioral context such as cost, authentication, or side effects.

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 tightly written sentences with no wasted words. The main capability and time scope are front-loaded, making the definition easy to scan.

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 explained. However, for a tool annotated as destructive and non-read-only, the description omits any disclosure of costs, side effects, or usage constraints, and it does not help distinguish this endpoint from its many siblings.

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 reported as 0%, so the description must compensate. It mentions a 'given domain' and a 'specific time period,' but does not explain the required target format, date_from/date_to constraints, rank_scale, or tag semantics, leaving most parameter meaning undocumented.

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 states a specific resource and scope: historical backlinks data back to 2019, with metrics like backlinks, new/lost backlinks, and referring domains. It is clear what the tool does, though it does not explicitly differentiate itself from sibling history/timeseries tools.

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?

The description gives no explicit when-to-use guidance, alternatives, or exclusions. It only implies historical data retrieval through the phrase 'historical backlinks data back to the beginning of 2019,' leaving the agent to infer when to choose this over other live backlinks endpoints.

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