git_repo_status

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

With no annotations, the description must carry the burden of behavioral disclosure. It only says 'show', implying read-only, but does not explicitly state non-mutation, no side effects, or any constraints like requiring a valid git repository or permissions. No additional behavioral traits are revealed.

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 with zero waste. It directly states the tool's output scope without filler. Every word contributes to understanding.

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 status tool, this is adequate but not complete. It tells what it shows but does not describe the return format, error behavior, or how repo_path is used (e.g., defaults to current directory). With no output schema, the agent lacks information about what to expect from the call.

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 description coverage is 0%, so the description must compensate. It does not mention the repo_path parameter at all, nor its default behavior. While repo_path is self-explanatory from the name, the description adds no meaning beyond the schema, failing to compensate for the lack of schema descriptions.

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 shows staged, unstaged, and untracked files for a repo. This is specific and distinguishes it from siblings like git_diff_repo (differences) and git_log_repo (history). The verb 'show' and resource 'files' are unambiguous.

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?

No mention of when to use this tool versus alternatives. There is no guidance on when to prefer this over other git tools (e.g., git_diff_repo, git_stage) or any prerequisites like 'only use on a valid repo'. The description does not provide context for exclusion.

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