Mooring

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

With no annotations provided, the description carries the burden of disclosure. It lists what data is retrieved (branch, stash count, file states), implying a read-only inspection, but does not explicitly state safety guarantees, failure modes (e.g., non-git directory), or that it requires local git installation.

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 efficiently sized with two distinct sections. While the 'Args:' section is slightly unconventional for MCP (parameters are usually documented solely in the schema), it earns its place by compensating for the schema's lack of descriptions. No redundant or filler text.

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?

Given the low complexity (single parameter, read-only operation) and the existence of an output schema (per context signals), the description adequately covers the tool's purpose and parameter semantics without needing to detail return values.

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?

Input schema has 0% description coverage (only a title 'Repo Path'). The description compensates by documenting the single parameter in the Args section: 'repo_path: Path to local git repository', adding crucial context that this path must point to a git repository specifically.

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 this retrieves 'Enhanced git status' and lists specific data points returned (branch, ahead/behind, stash count, staged/unstaged/untracked files). However, it does not explicitly differentiate from sibling tools like 'repo_stash' (which likely manages stashes vs. just counting them) or 'repo_diff'.

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 'repo_diff' (for changes) or 'repo_log' (for history). There are no 'when-not-to-use' exclusions or prerequisites mentioned, such as requiring the path to be a valid git repository.

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