search_repos

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

The description discloses the core search behavior: query matching, optional language filtering, and sorting. It also implicitly signals a non-mutating operation via the verb 'Search.' However, with no annotations available, it omits potentially useful behavioral details such as rate limits, visibility constraints, or whether only public repositories are searched.

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 entire description is one front-loaded, concise sentence with no unnecessary wording. Every phrase contributes something meaningful: the resource searched, the query, the optional language filter, and the sort behavior.

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?

This is a simple read-only search tool with an output schema already present, so the description need not document return values. The main missing elements are sort value options and sibling-tool routing guidance, but an agent has enough information to invoke the tool correctly.

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 is responsible for explaining parameters. It adds meaning to query, language, and sort, but it does not explain the limit parameter's purpose or what sort values are accepted, leaving the parameter explanation incomplete.

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 and resource: 'Search GitHub repositories matching query, optional language filter, and sort order.' It clearly identifies what the tool affects and differentiates it from sibling tools like search_code and search_local_files, which operate on code or local files rather than repositories.

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 intended use is implied: use this tool when looking for GitHub repositories. However, the description never explicitly mentions when to choose this over search_code or search_local_files, nor does it state any exclusions or alternative conditions.

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