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

The description implies a read-only retrieval ('provide you with a list of backlinks'), but annotations declare readOnlyHint=false and destructiveHint=true. This is a direct contradiction; the description fails to disclose any destructive behavior and instead suggests a safe read operation.

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?

A single, front-loaded sentence with no wasted words. It efficiently conveys the core purpose, though its brevity comes at the cost of detail covered elsewhere.

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?

The core purpose is clear and the rich input schema plus output schema cover most operational details. However, the description does not mention that the body accepts multiple targets (array), nor does it distinguish from sibling tools, and the annotation contradiction adds confusion.

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?

With schema description coverage at 0% for the top-level 'body' parameter, the description should compensate but does not. It only vaguely references 'the specified domain, subdomain, or webpage' without clarifying the body array, filters, pagination, or any of the rich nested parameters documented in the schema.

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 verb (provide a list) and resource (backlinks) with scope (domain, subdomain, or webpage). However, it does not differentiate from siblings like bulk_backlinks_live or anchors_live, leaving the agent to infer which backlinks endpoint fits best.

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?

No guidance is given on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only states what it does, not when it is the right choice.

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