Export Backlinks Data

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

The description notes async behavior and task ID, but lacks details on rate limits, data volume limits, or how to use the task ID (e.g., referencing DATA_getBacklinksExportStatus). No annotations exist, so the description carries full burden.

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?

Single sentence with 14 words, front-loaded purpose, zero redundancy.

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?

Missing critical context for an async tool: no mention of status-checking endpoint (DATA_getBacklinksExportStatus) or how to handle the task ID. Incomplete for its complexity.

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 coverage is 50% (only 'target' described). The description adds no parameter information beyond the schema. Enum values for 'mode' are not explained, and 'target' remains vague. Compensation is insufficient.

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 clearly states it retrieves large-scale backlinks asynchronously and returns a task ID. This specifies the verb and resource, distinguishing it from synchronous siblings, but lacks explicit sibling differentiation.

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 on when to use this tool versus alternative backlink tools (e.g., DATA_getAllBacklinks). The description does not mention prerequisites or typical scenarios.

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