Repository summary

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds the analysis scope (calendar months ending at most recent commit) and the 'good first call' hint, but says nothing about cost, performance on large repos, or error behavior when a path is not a git repo. Adequate but not rich.

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 enumeration of returned fields is front-loaded and each item earns its place for a summary tool. It is a single dense sentence plus a short routing hint; only the long itemized list risks being more detail than strictly needed.

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?

With an output schema present, the description needn't explain return values, and annotations cover safety; params are fully documented in the schema. The one remaining gap is usage routing — no mention of when a sibling like health_report or commit_details is the better choice.

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 100%: repo_path's sub-folder scoping rule and include_merges' rationale are already fully documented in the schema. The description adds no syntax or behavioral detail beyond what the input schema provides, so 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 resource (local git repository) and enumerates exactly what the summary contains: branch, commit counts, first/last commit, author count, top contributors, monthly activity. Sibling tools (health_report, bus_factor, hotspots) cover narrower analyses, and the 'Overview... Good first call' framing clearly positions this as the entry point.

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?

'Good first call' gives a clear when-to-use signal and implicitly positions it ahead of the other ten repository tools. It stops short of naming alternatives or stating when not to use it (e.g. for a single file or commit), so it lacks explicit routing.

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