git_commit

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

No annotations are provided, so the description carries the full burden. It discloses the main action (staging and committing) but does not explain side effects like creating a commit object, behavior when the files list is empty, or failure conditions. For a mutating operation, this is a significant transparency 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 a single sentence with no redundancy. It is front-loaded with the action and resource, making it highly concise and scannable.

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 git commit tool with no output schema and no annotations, the description omits key operational details: what happens if files is empty, what 'conventional commit' format is used, and how message and autoGenerate interact. This makes it incomplete for robust agent use.

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 descriptions are absent (0% coverage), so the description must compensate. It adds meaning by indicating that 'files' are the targets of staging/committing and that messages are auto-generated. However, it does not clarify the 'message' parameter or how it interacts with 'autoGenerate', leaving ambiguity.

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 'Stage and commit' with a clear resource ('files') and mentions the unique behavior of auto-generating a conventional commit message. This clearly distinguishes it from sibling tools like git_push, git_pull, and git_status.

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 usage is implied: it is for staging and committing files locally. However, the description does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions or prerequisites (e.g., that a git repository must exist).

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