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

No annotations exist, so the description carries the full behavioral burden. It indicates the output topics but does not disclose how the query behaves with an empty q, whether it hits the live GitHub API, rate-limit implications, error behavior for invalid repos, or any other operational traits.

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 very short and front-loaded, with no filler words. It sacrifices completeness for brevity, but as a concise summary it is effective and easily scannable.

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?

Given the large sibling set and no annotations, the description is too sparse to fully support tool selection and correct invocation. The output schema helps with return values, but usage context, parameter semantics beyond format, and alternative routing are missing.

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 0%, but the parenthetical '(owner/repo)' adds essential meaning to the q parameter. It does not explain what happens when q is empty (the default) or enforce the format at the schema level, which leaves a notable gap for a one-parameter tool.

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 specifies a clear resource (GitHub repo) and the type of data returned (stars, languages, license, activity), plus the expected owner/repo format. It does not use an explicit verb like 'get', and the sibling 'github' could overlap, but the field list provides enough distinction.

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 when-to-use or when-not-to-use guidance is provided. With many GitHub-related siblings such as github_code, githubsearch, ghorg, and ghlanguages, the description does not help an agent choose this tool over alternatives.

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