git_diff_summary

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: output is bounded and excludes patch contents. However, 'bounded' is never quantified (no cap, truncation, or pagination behavior), and nothing is said about what repository state or working tree the diff is taken against.

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?

A single twelve-word sentence that front-loads the resource and immediately qualifies it with the key constraint. Nothing is redundant and nothing pads it.

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?

An output schema exists, so return values need no explanation, and with zero parameters the surface area is small. The remaining gap is that 'bounded' is unquantified and the diff baseline is unstated, which matters given the dense git_* sibling cluster.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The one caveat is that with no arguments, the implicit target (working tree vs. staged vs. HEAD) is undefined anywhere in the definition.

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 gives a specific verb ('Return') and resource ('diff statistics') with a scope qualifier ('bounded') and an explicit exclusion ('without patch contents'). That exclusion implicitly separates it from git_diff, but it never names git_diff_stat or git_diff, so the agent must infer the boundary itself.

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?

Usage is only implied: an agent can infer you call this when you want diff numbers but not patches. There is no explicit 'use this instead of git_diff/git_diff_stat when...' statement and no stated preconditions, so the routing decision is left to inference.

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