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

No annotations are provided, so the description carries full burden. It only states the core logic (find source pages with intersection) but discloses no behavioral traits such as permissions, rate limits, data freshness, or whether results are read-only. Important context is missing.

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, front-loaded with the action phrase 'Find source pages that...', and contains no redundant words. It efficiently conveys the core purpose.

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 (18 parameters, no annotations, no output schema), the description is too brief. It does not cover pagination, sorting, filtering options, result format, or error scenarios. Essential context for effective use is lacking.

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%, meaning no parameters are described in the schema. The description only implicitly refers to 'targets' and 'exclude_targets' via mentions of 'competitor targets' and 'excluded/user targets'. It adds minimal meaning beyond the schema; for a tool with 18 parameters, the description fails to clarify their roles.

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 the tool finds source pages linking to competitor targets but not excluded/user targets, then prioritizes link-gap outreach and quality review. It uses a specific verb ('find') and resource ('source pages'), and distinguishes from sibling backlinks tools by focusing on intersection logic.

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 description implies usage for link-gap outreach and quality review but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. No alternative tools are referenced.

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