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

With no annotations, the description carries the behavioral burden; it usefully discloses that the search targets public repos and code content rather than issues or repository metadata. It does not mention rate limits, authentication, or whether GitHub dork operators are supported, but the core read-only behavior is evident from the description.

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 one compact sentence with the action and scope front-loaded, and no filler. The opening label 'GitHub Dork Search' is somewhat redundant with the tool name, but the explanatory clause earns its place.

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 one-parameter search with an output schema, the core invocation is understandable. The main gaps are sibling routing and query-syntax guidance, which matter given the large family of GitHub search tools surrounding this one.

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%, so the description must compensate. The phrase 'target string exposure' clarifies that q is the string to search for, which adds meaning beyond the bare schema. However, it does not specify whether q accepts GitHub search operators or how the empty default value behaves.

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-resource pairing: it searches GitHub code for a target string in public repos. The 'dork' framing signals a security-motivated search, but it does not explicitly differentiate itself from similar siblings such as github_code, githubsearch, or gh_secret_scan.

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?

No guidance is provided about when to prefer this tool over the many GitHub-related siblings. The text implies code search, but it does not state exclusions such as 'for secret scanning, use gh_secret_scan' or 'for repository metadata, use githubsearch'.

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