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 states that the scan targets public repos for secrets, but it does not mention authentication needs, rate limits, failure behavior, or whether the operation is purely read-only.

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 and easy to parse, but the leading 'GitHub Secret Scan:' phrase repeats the tool title and adds little value. Overall it is compact with no unnecessary elaboration.

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 is too thin to fully equip an agent given the absence of annotations and an undocumented parameter. It does not explain what q should contain, what output to expect, or how this differs from the many similar GitHub/secret-scan siblings.

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 one parameter, q, with no description, and schema description coverage is 0%. The description loosely implies q identifies a GitHub user, but it does not specify the expected format (username vs. URL), whether it is required, or what the empty default means.

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 names a specific verb and resource: 'Scan GitHub user's public repos for leaked secrets/passwords.' This is clear enough to understand the tool's basic function, though it does not explicitly distinguish it from sibling tools like gh_dorking or api_key_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 given on when to prefer this tool over related alternatives. It does not state what inputs are valid, whether the user must provide a GitHub username or repository URL, or when a sibling tool like gh_dorking would be more appropriate.

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