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

Annotations cover read-only and non-destructive nature. The description adds useful behavioral context beyond annotations: the async pattern (polls up to ~10s, returns job_id if still running) and quota impact. These are valuable operational details not present in structured fields.

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 tightly written in three sentences, front-loading the core purpose and filter condition. Every sentence contributes essential information—what it does, why it's valuable, and operational notes—without fluff.

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?

The description covers the filter logic, async behavior, and quota implication. It does not explicitly state the return value on success (presumably a list of domains), but the tool name and purpose imply this. Given the absence of an output schema, a slight gap exists but overall it is sufficiently complete.

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?

The input schema has 100% coverage, so parameters are already documented. The description reinforces the meaning of competitor_domains by explaining the filter logic (link to every competitor but not to user), but does not add new semantic depth beyond what the schema and purpose already provide.

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 explicitly states the tool filters gap analysis to linking domains that link to every competitor but not to the user, naming the specific resource and filter condition. It distinguishes itself from the sibling crawlgraph_gap_analysis by framing it as the 'warm-outreach play' and referencing the broader tool.

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 clearly identifies when to use it (for highest-conviction outreach candidates) and references the sibling crawlgraph_gap_analysis for the general case, implying an alternative. It does not explicitly list exclusions, but the purpose and reference to the sibling provide enough guidance for an agent to select correctly.

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