git_reset

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

No annotations provided. The description covers execution timing and timeout behavior, which is useful for non-functional traits, but omits the actual behavioral impact of git reset (e.g., destructive changes to HEAD, index, working tree).

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 verbose about execution timing but lacks a concise definition of the core functionality. Important information is missing, and the structure prioritizes secondary details over primary purpose.

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 the absence of annotations and the presence of an output schema, the description fails to provide essential context about the git reset operation. The agent cannot understand the tool's effect or return value.

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%, and the description does not explain the git-related parameters (ref, mode, path, paths). It only discusses execution timing parameters, which are already in the schema but not explained in context of the operation.

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 state what git_reset does; it only mentions 'Kali Agent MCP tool: git_reset' without explaining the git operation. The name implies git reset, but the agent cannot discern purpose from the description alone.

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 on when to use git_reset versus sibling tools like git_checkout, git_restore, etc. The description only advises on execution timing parameters, not the tool's domain of use.

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