Get GitHub repo status

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

No annotations are provided, so the description carries the full burden. It describes the tool as inspecting local repository data, implying a read-only operation with no side effects, but does not explicitly mention that it is non-destructive or whether it requires network access or specific permissions. Adequate but could be more explicit.

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, concise sentence of 13 words, front-loaded with the main verb and resource. No extraneous information is present, and every word contributes to clarity.

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 simple inspection tool with one parameter and no output schema, the description covers the key aspects: what is inspected (status, branch, remotes, upstream, allowed roots). It does not describe the return format, but given the low complexity, it is reasonably complete.

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 description adds minimal meaning beyond the input schema. The schema already describes the repoPath parameter with similar language ('Path to a local repository inside the configured allowed roots'). With 100% schema coverage, the baseline is 3, and the description does not significantly enhance understanding.

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 clearly states the tool inspects a local Git repository's status, branch, remotes, upstream, and MCP allowed roots. It uses a specific verb ('inspect') and resource ('local Git repository'), and effectively distinguishes from sibling tools that focus on creating or modifying branches and pull requests.

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 inspecting repo status but does not explicitly state when to use this tool over siblings or provide alternatives. No guidance on when not to use it is given, though the context is clear from the sibling names.

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