Git Log

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

The readOnlyHint=true annotation already establishes that this is a non-mutating read, so the description's added burden is small. It does contribute useful context by disclosing the 'approved workspace repository' access constraint and the word 'recent', which signals a bounded rather than full history. It says nothing about ordering, truncation, or empty-repo behavior beyond that.

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 with no filler; the scope constraint is placed where it is read first. It is arguably too terse for the parameter gaps it leaves, but nothing in the sentence is wasted.

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 two-parameter read tool with an output schema and a readOnlyHint, the definition covers the essentials of what the tool does and where it may run. The missing piece is parameter behavior, particularly the commit limit and the meaning of an empty project_path, which neither schema nor description resolves.

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 0%, so the description must carry parameter meaning, and it largely does not. 'recent' gestures at max_commits (default 15) but never explains the limit or its default, and 'approved workspace repository' only loosely implies project_path without saying what format it takes or what the empty default means.

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 names a specific verb and resource ('Get recent git commit history') and bounds the scope to an 'approved workspace repository', which is enough to separate it from siblings like git_diff and git_status that inspect working-tree state rather than history. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

There is no statement of when to reach for git_log versus git_diff, git_status, or check_git_updates; the only implied condition is that the repository must be 'approved'. An agent must infer the use case from the name alone.

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