git_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating operation. The description adds minimal context by specifying the resource ('working tree status') but does not reveal any additional behavioral traits such as whether it includes staged, unstaged, or untracked files, or any limitations. The description is consistent with annotations, so no contradiction.

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, well-formed sentence that delivers the core purpose without any wasted words. It is front-loaded and immediately understandable, making it an excellent example of conciseness.

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 tool's low complexity (one parameter, no output schema) and the presence of annotations that cover the safety profile, the description is minimally adequate. However, it is missing useful context such as what exactly the status includes (e.g., branch, staged, unstaged, untracked files) and how repo_path should be specified. An agent could call the tool correctly but might lack expectations about the returned output.

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%, and the description does not mention or explain the 'repo_path' parameter. Although the parameter name and title 'Repo Path' are somewhat self-explanatory, the description fails to compensate for the lack of schema documentation, leaving the agent without guidance on how the path should be formatted or validated.

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 uses a specific verb ('Shows') and resource ('working tree status'), clearly indicating what the tool does. While it does not explicitly differentiate itself from sibling tools, 'working tree status' is a distinct concept that separates it from git_diff and git_log, making the purpose 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention git_diff for viewing changes, git_log for history, or any conditions that would make git_status the preferred choice. The usage context is only implied by the tool name and basic description.

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