Get 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, which covers the safety profile. The description reinforces 'read-only' and adds the valuable behavioral constraint that the path must be inside an allowed root, providing context beyond the structured fields.

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 that precisely conveys the operation and constraints with no wasted words. It earns every word and is immediately scannable.

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 one-parameter, read-only tool with comprehensive annotations and no output schema, the description adequately covers the operation, scope, and safety. It does not detail the return format, but 'git status' is a well-known command, so the description is sufficient for an agent to understand what to expect.

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 schema already fully describes projectPath as an absolute project directory path (100% coverage). The description adds the extra semantic requirement that the path must reside within an allowed root, which is not present in the schema description, thus providing additional meaning.

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 operation ('run a read-only git status'), the target resource ('project directory'), and the scope constraint ('inside an allowed root'). This distinguishes it from sibling tools like get_git_diff, which compares changes rather than showing status.

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 gives clear context that this is a read-only operation and is restricted to allowed roots, implying it should be used for checking repository status within permitted paths. However, it does not explicitly name alternatives or state when not to use it, such as comparing against get_git_diff.

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