Git PR context

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

readOnlyHint=true already declares the safety profile, and the description usefully specifies that the output is an aggregate of three artifacts (commits, file statuses, diffstat) rather than a raw diff. It doesn't mention size/truncation behavior for large branches, which is the main remaining gap.

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 front-loaded sentence that puts the resource and range before the use case. Minor deduction for the trailing ellipsis, which leaves the enumeration looking truncated rather than finished.

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?

Read-only, fully documented parameters with sensible defaults, and an output schema that carries return-value detail. The description is close to complete for this complexity; only edge-case behavior on very large comparisons is unaddressed.

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 coverage is 100%, so base, head, and cwd are already documented with defaults. The description's 'base...head' phrasing reinforces the range semantics but adds no format details beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Collect') and concrete resources (commit list, changed files with status, diffstat) over a base...head range, plus the intent ('for writing a PR description'). It implicitly separates itself from single-purpose siblings like git_log and git_diff by being an aggregate, but never names them explicitly.

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 parenthetical 'for writing a PR description' gives a use context, which is useful. However there is no explicit guidance on when to prefer this over git_log, git_diff, or git_status, nor any stated exclusions or prerequisites.

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