Off-page gap finder

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool is non-destructive ('does not publish anything or contact anyone') and describes what it returns ('gaps and priorities'). This adds useful context beyond the schema, though it could mention whether any crawling or network requests are made.

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 four sentences long, each earning its place: main action, rationale, when-to-use, and behavioral boundary. It is front-loaded with the core verb and resource, with no wasted words.

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 simple single-parameter tool with no output schema, the description covers all essential decision-making information: what it finds, why it matters, when to use it, and what it returns. The high-level return phrase 'gaps and priorities' is adequate for an agent to select and 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 coverage is 100%: the single required `url` parameter already has a clear description and example. The tool description adds no additional parameter-level semantics, but the parameter is self-explanatory, so the schema alone is sufficient.

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 opens with the specific verb 'Finds' and names concrete resource types (review platforms, directories, communities, 'best of' roundups), making it unmistakably distinct from sibling tools like shopping or crawler watch. It also clarifies the scope as 'OUTSIDE its own website,' further sharpening the purpose.

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 gives an explicit trigger: 'Use this when a site is technically perfect yet still never cited.' It also provides a when-not by stating that the tool 'does not publish anything or contact anyone,' so the agent knows it is only for analysis, not action.

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