Git diff

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

While annotations confirm read-only behavior, the description only adds the '--no-color' flag. It does not explain what the diff compares (e.g., working tree vs index, or vs HEAD), nor does it describe the output format beyond no color.

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 extremely short (one sentence), which is efficient but omits important details. It is front-loaded with the core action, but lacks completeness. A slightly longer description would be more useful.

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 tool with one required parameter and an output schema, the description is still incomplete. It fails to explain what the output represents (e.g., unstaged changes, staged changes) and how to interpret it. The existence of an output schema somewhat mitigates this, but the description should still provide high-level context.

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 only parameter, workspaceId, has no schema description (0% coverage). The description adds the context 'inside an open workspace', implying the workspace must be open, but provides no further details like whether it is a folder or a repository identifier.

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 action ('Run'), the specific command ('git diff --no-color'), and the context ('inside an open workspace'). It distinguishes from sibling tools like git_status by naming a different git command.

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 guidance is provided on when to use this tool versus alternatives (e.g., git_status, drift_check). There is no mention of prerequisites, limitations, or exclusions.

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