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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds useful context that links are sampled and include anchor text and nofollow evidence, but it does not explain sampling behavior, pagination, limits, or what the response looks like.

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?

It is a single short sentence with no filler, so it is concise. However, it is an incomplete fragment rather than a front-loaded definition, and the extreme brevity leaves important invocation details unstated.

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?

For a seven-parameter tool with low schema description coverage and no output schema, the description is too thin. It does not explain parameter meanings, filtering behavior, pagination, or how the sampled results should be interpreted.

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 only 29% across seven parameters, so the description needs to compensate for undocumented fields like area, days, limit, offset, and workspace. It only indirectly references direction through 'incoming/outgoing' and says nothing about the required URL or the other filters.

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 identifies the resource as incoming/outgoing page links with anchor text and nofollow evidence, which is specific data. However, it is a noun phrase rather than a clear verb+resource statement and does not distinguish this from sibling tools such as list_connections.

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?

There is no indication of when to use this tool instead of list_connections, verify_links, backlink_gap, or other connection-related siblings. The description provides no usage context, prerequisites, or exclusions.

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