git_log

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

With no annotations provided, the description carries full burden. It discloses execution timing behavior but omits core functionality—what the tool does (e.g., return git log entries). The agent cannot infer what data it outputs or what side effects occur, which is critical for a tool with 8 parameters and no schema descriptions.

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 concise but misallocated: it front-loads boilerplate 'Kali Agent MCP tool' and immediately dives into timing details, neglecting the tool's primary purpose. A single paragraph is reasonable, but the content ordering and focus reduce effectiveness.

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?

Given 8 parameters, 0 required, and an output schema, the description should explain the tool's overall function and key parameters. It fails to state that git_log retrieves commit logs, leaving the agent uninformed about the tool's purpose. The timing advice is helpful but insufficient for complete understanding.

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 should compensate. However, it only partially explains the timing parameters (on_timeout, timeout_seconds, etc.) while ignoring core parameters like ref, path, and limit. These must be inferred from names, which is unreliable for an AI agent.

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 does not explicitly state that git_log retrieves commit history; it focuses entirely on execution timing configuration. The purpose is merely implied by the tool name, which is insufficient for an AI agent to confidently select it over siblings like git_diff or git_show.

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?

The description provides guidance on timing parameters and on_timeout options, but it offers no context about when to use git_log versus other git tools. There is no mention of its primary use case (e.g., viewing commit logs) or alternatives, limiting the agent's ability to choose appropriately.

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