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

No annotations are provided, so the description carries the full burden. The word 'manual' and the verb 'builds' imply the tool generates links for the user to open rather than automatically scraping results, which is a useful behavioral hint. However, it does not state whether the tool makes network requests, what output format is returned, or any rate-limit or safety considerations.

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 concise sentence with no obvious padding. However, the opening 'Search Dorks:' partially duplicates the tool name before the actual statement, preventing a perfect score for structure.

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?

This is a simple one-parameter utility, and an output schema exists, so return values do not need to be explained in the description. Still, the description leaves the meaning and required format of 'q' underspecified, and does not clarify what set of dorks or link sources is included, making it only minimally viable.

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 schema has a single optional 'q' parameter with 0% description coverage, so the description must compensate. It never explicitly explains that 'q' is the dork/search query, nor does it mention accepted formats, URL encoding, or examples. The meaning is only inferable from the tool name and 'search links.'

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 states a clear verb ('Builds') and resource ('manual OSINT search links'), making it evident that this tool constructs search-engine dork links rather than performing a search itself. It does not, however, fully differentiate itself from similarly named search-related siblings such as gh_dorking or urlscansearch.

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, and no mention of whether 'dorks' expects a simple keyword or a full search-operator syntax. Given the large sibling list, the absence of explicit when-to-use or when-not-to-use guidance is a significant gap.

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