git_log

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — no ordering (newest-first?), no pagination semantics for the limit, no indication of what a truncated history means.

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?

It is a single four-word fragment with zero filler, so it is maximally brief, but brevity here comes from under-specification rather than disciplined editing.

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 simple read-only tool this could be adequate, but with no output schema and one undocumented parameter, the description leaves the return shape, ordering, and limit behavior entirely unspecified.

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?

With only 50% schema description coverage, the description is expected to compensate, but it mentions neither parameter. The 'path' parameter is documented in the schema, while 'limit' has no description anywhere, so an agent cannot tell what it caps or how it interacts with the default of 15.

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 is a bare noun phrase, 'Recent commit history,' that essentially restates the tool name git_log. It gives no verb, no scope (which repo, which branch, whole history vs. HEAD), and does nothing to distinguish it from siblings like git_status, git_diff, or git_commit.

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 call this versus git_diff, git_status, or git_commit. The agent must infer that this returns a listing of past commits rather than diffs or working-tree state, with no stated conditions or alternatives.

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