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, but it only lists data categories rather than explaining actual behavior. It does not mention whether the tool aggregates multiple endpoints, performs lookups by username, requires authentication, or has rate-limit 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 extremely short and front-loaded, with no wasted words. While it is arguably too terse, every token contributes to conveying the tool's domain and scope.

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 one-parameter tool with an output schema, this is a low-complexity case, but the description still fails to define the parameter and how to invoke the tool. The output schema reduces the need to explain return values, but the missing input semantics makes the overall description incomplete for reliable tool selection and invocation.

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 input schema has one parameter, q, with no description and 0% schema description coverage, so the description must compensate. It never explains what q should contain—whether it is a GitHub username, organization name, repository path, or search query—leaving the agent unable to infer correct usage.

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 communicates that this tool performs GitHub reconnaissance over profiles, repositories, and languages, which is more informative than a tautology. However, 'Recon' is a vague, non-specific verb-like label, and the description does not explicitly differentiate this tool from the many GitHub-specific siblings such as ghrepo, ghlanguages, githubsearch, or github_trending.

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 usage guidance is provided. The description does not state when to choose this tool over its GitHub siblings, nor does it mention any exclusions or alternatives, despite the sibling list containing many closely related tools that likely overlap in purpose.

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