Backlinks All

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

With no annotations provided, the description carries the transparency burden. It does say 'Fetch', which correctly signals a read-only operation, and 'single target' clarifies the input scope. However, it does not disclose the shape of returned backlink records, pagination behavior, or the 'per_domain' caveat that results may exceed 100 records.

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?

The description is a single, well-organized sentence that front-loads the action and resource, then enumerates the filter dimensions in a skimmable list, and ends with the exact endpoint. Every element earns its place and there is no redundant filler.

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 tool with 17 parameters and no output schema, the one-line overview is useful but not fully complete. The schema documents all parameters, but the description does not describe the expected result structure, pagination semantics, or behavior when optional filters are omitted. It is adequate for invocation but relies heavily on the schema and agent inference.

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 the parameters are already well documented with enums, defaults, ranges, and meanings. The description adds only a high-level grouping of filters (rank, URL/anchor, nofollow) without providing syntax or interaction details. Baseline 3 is appropriate because the schema carries the semantic weight.

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 names the exact operation and resource: 'Fetch backlinks pointing to a single target'. It also lists the distinguishing capabilities (sorting, limits, rank filters, URL/anchor filters, nofollow filter), which clearly separates it from sibling aggregation tools like backlinksSummary or backlinksRefdomains. The endpoint reference 'v1/backlinks/all' removes ambiguity about which API function is being invoked.

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 feature list implies this is the raw backlinks endpoint, and 'single target' gives some scope context. However, the description never names sibling alternatives or states when not to use it, so an agent must infer the distinction from the tool name and sibling list rather than from explicit guidance.

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