personal_git_commit

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

The description adds value beyond the annotations by stating the operation is local and never pushes or publishes. However, it does not explain the critical behavior of the 'execute' flag—what exactly 'plan' means versus 'explicitly create'—and whether the default mode makes no changes at all. Given all annotations are false, this is a meaningful gap.

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 two sentences with no filler. The primary action is front-loaded, and the key constraint—no pushing or publishing—is stated crisply.

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 tool with four parameters, no output schema, and no safety annotations, the description is too thin. It covers the local and non-publishing nature but omits the execution semantics of 'plan' vs. 'execute', how paths are treated, and what the agent can expect as a result. This is insufficient for reliable invocation.

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 provides no information about any of the four parameters: repo_path, paths, message, or execute. The description does not compensate for the schema's lack of parameter documentation, leaving agents to rely solely on property names.

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 states the specific verb 'create' with a clear resource ('local commit'), and clarifies the dual mode ('Plan or explicitly create'). It also scopes the operation to 'an allowlisted Git root' and explicitly rules out push/publish, which separates it from potential sibling 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?

The description gives clear context: use this tool for local commits, and the statement 'This never pushes or publishes' signals when not to use it. It does not name alternatives like personal_git_snapshot, but the scope is sufficiently explicit for selection.

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