List Github Repos

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

The description and annotations are consistent: 'Search' implies a read-only operation, and readOnlyHint=true confirms no side effects. However, the description gives no additional behavioral context such as whether results are paginated, sorted, or limited by the installationId, so it does not go beyond the annotations.

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 concise and free of unnecessary wording. However, it is so brief that it sacrifices important context, which prevents a higher score for structure despite being well-formatted.

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 no output schema and no parameter descriptions, the description is far too incomplete for an agent to use confidently. It does not clarify what the returned data looks like, what the parameters mean, or how the tool fits into the broader GitHub integration workflow.

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% and the description does not explain any of the four parameters. While names like q and limit are somewhat self-explanatory, the required workspaceSlug and installationId are not, and no parameter descriptions are provided. The description fails to compensate for the complete lack of schema documentation.

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 'Search GitHub repositories' identifies a clear verb and resource, but it lacks essential scope: it does not mention that the search is scoped to a workspace or GitHub installation, which is implied by the required workspaceSlug and installationId parameters. It is distinguishable from sibling tools only by its name, not by a precise purpose statement.

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 provides no guidance on when to use this tool versus alternatives like getGitOverview, linkGithubIntegration, or runGitAction. There is no mention of typical use cases, prerequisites, or whether this should be used before linking a GitHub integration.

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