git_log

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only operation, what happens if the path is not a repo or the repo is empty, how history is ordered, or what fields each commit entry contains. It only contributes the limit range (1-200), which is useful but far short of the disclosure needed for an annotation-free tool.

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 purpose sentence is front-loaded and the two parameters are listed compactly with no filler. The Args block is slightly verbose for two parameters but nothing 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?

With no annotations and no output schema, the description should tell the agent enough to call and interpret the tool. It covers both inputs and scope, but never indicates the shape of a returned commit (hash, author, message, date) or the ordering, leaving interpretation of results to guesswork.

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 compensate, and it largely does: it defines 'path' as repo path relative to the workspace root and 'limit' as the number of commits, with a valid range of 1-200. It omits the schema defaults (path='.', limit=10), so an agent cannot infer default behavior from the prose alone.

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 and resource: 'Get recent commit history for a repository inside the workspace.' An agent can distinguish this from git_status and git_diff by the resource (commit history vs. working-tree state vs. change content). It does not, however, explicitly contrast itself with the neighboring git_* tools.

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 guidance on when to use git_log versus git_diff, git_status, git_branches, or git_current_branch. The word 'recent' hints at a recency scope but no conditions, prerequisites, or alternatives are named.

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