git_log

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

The description is consistent with readOnlyHint, idempotentHint, and destructiveHint=false, but it adds no behavioral context beyond what the annotations already state. It does not mention default truncation, output characteristics, or repository-scope behavior.

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 description is short, but it is under-specified rather than appropriately concise. A single five-word phrase is not enough structure for a tool with four parameters and several closely related sibling tools.

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 output schema and no sibling differentiation, the description leaves the agent to infer what the logs contain and when this tool is appropriate. The annotations cover safety, but the description alone does not make the tool's usage context complete.

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 only 50%; end_timestamp and start_timestamp are documented, but repo_path and max_count are not. The tool description itself provides no parameter meaning, so it does not compensate for the undocumented parameters.

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 uses a specific verb and resource ('Shows the commit logs'), so an agent can understand the basic operation. It does not differentiate from siblings like git_show or provide scope, but the action and resource are clear.

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?

No guidance is given about when to use git_log instead of sibling tools such as git_show, git_diff, or git_status. There are no conditions, exclusions, or alternative pointers.

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