github_search_repositories

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

With no annotations provided, the description should disclose behavioral traits such as whether authentication is required, whether the operation is read-only, or any rate limits or pagination behavior. The description only states the search action and gives examples, adding no context about side effects, safety, or constraints. This is a notable gap given the presence of a github_auth_status sibling tool.

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, front-loaded sentence that immediately focuses on the primary action and includes helpful query examples. There is no filler or redundant information; every word adds value.

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 provides enough to understand the tool's core purpose, and the existence of an output schema covers return value specifics. However, the lack of usage guidance, parameter clarification for 'limit', and behavioral context (e.g., auth) makes it incomplete for an agent to confidently invoke the tool without additional assumptions. For a simple search tool, it is minimally adequate but has clear gaps.

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 description coverage is 0%, so the description must compensate for both parameters. It effectively explains the 'query' parameter with examples, but it does not explain the 'limit' parameter at all. The schema defines limit as an integer with default 5, but without a description, the agent cannot know that limit likely controls the maximum number of results returned.

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 for GitHub repositories') with clear resource (GitHub repositories) and method (by query). Examples of query formats help differentiate it from sibling tools like github_get_repository_info or github_list_files, since this is the only search tool among them.

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?

The description implies usage for searching repositories and provides query examples, but it does not explicitly state when to use this tool instead of alternatives like github_get_repository_info or github_list_files. There is no mention of when not to use it or any prerequisites (e.g., authentication), though the examples offer some contextual hints.

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