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

With no annotations provided, the description carries the full burden of disclosing behavior; however, it only restates the tool name. It does not mention pagination, filtering, required parameters, authentication, or any side effects, so the agent has no insight into what the tool does beyond its label.

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 sentence, but it is under-specified rather than appropriately concise. It offers no structural value, such as key constraints or examples, and is not 'front-loaded' with useful information because it contains no information beyond the title.

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?

Given the tool's complexity (15 parameters, no output schema, no annotations) and the presence of many sibling tools, the description is completely inadequate. It does not explain what backlink opportunities are, how to use the tool, or what the response will contain, making it nearly impossible for an agent to invoke it correctly.

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 0%, and the description provides no parameter explanations. With 15 parameters (4 required) and no guidance on how to fill them, the agent cannot understand meaning, formats, or relationships among parameters. The description completely fails to compensate for the schema's lack of descriptive detail.

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 'Get backlink opportunities.' is a direct restatement of the tool title and provides no differentiation from sibling tools like get_community_opportunities or get_content_opportunities. It conveys the verb and resource but adds no specificity about scope or purpose beyond the name itself.

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 guidance on when to use this tool versus alternatives. No context about typical use cases, prerequisites, or exclusions is provided, leaving the agent without any decision support for selecting this tool among its siblings.

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