git_git_commit_all

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

No annotations are provided, so the description must disclose behavior. It indicates a mutation (staging and committing) but lacks details on side effects, authorization needs, or whether it pushes. The description is too sparse for a mutable operation.

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?

Two sentences, no wasted words. The use case is front-loaded. Perfectly concise for a simple tool.

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?

The tool is simple with one parameter and an output schema (so return values not needed). The description covers purpose and usage, but lacks behavioral transparency and parameter detail. It is adequate but not thorough.

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?

The single parameter 'message' has a description coverage of 0%, but the description clarifies it is the commit message. No format, length, or example details are given. The added value over the schema is minimal.

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 clearly states the tool stages all changes and commits with a message. The verb 'commit' and resource 'all changes' are specific. It distinguishes itself from other git siblings (e.g., git_git_checkout_branch) by being the only commit tool.

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 when to use it: 'Use before making risky changes as a checkpoint.' This gives clear context but does not explicitly mention when not to use or suggest alternatives like git_safe_write_with_checkpoint.

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