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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the search action and does not mention authentication needs, rate limits, default behavior when q is empty, pagination, or any side effects; 'search' implies read-only behavior but little beyond that is disclosed.

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 short and front-loaded, with 'GitHub Repo Search' introducing the resource and the second clause adding the keyword behavior. It is efficient, though the leading phrase is somewhat redundant with the tool name and title.

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?

With a single optional parameter, an existing output schema, and no nested objects, the description is adequate for making the call. It is incomplete for tool selection because it does not distinguish githubsearch from its GitHub siblings or clarify empty-query behavior.

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 exposes only q (string, default ''), and schema_description_coverage is 0%, so the description must compensate. 'by keyword' does convey the core meaning of q, but it provides no query-syntax details, examples, or behavior when q is omitted, so compensation is only partial.

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 specific action ('Search') applied to a specific resource ('GitHub repos') using 'keyword', so an agent knows the core operation. It does not explicitly contrast itself with the many GitHub-related siblings like github_code, ghrepo, and github_code search variants, so it stops short of a 5.

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 about when to use githubsearch versus the numerous GitHub sibling tools, such as github_code, ghrepo, or github_trending. The intended use is only implied by the phrase 'repo search', with no explicit when-to-use or when-not-to-use context.

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