git-flow

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It covers the basic actions (add all, commit, push) but omits important details: side effects (e.g., what happens on push conflicts), failure modes (e.g., no changes to commit), required permissions, or whether the directory must be a git repository.

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 extremely concise—one sentence clearly communicating the tool's purpose and workflow. Every word earns its place, with no redundancy or unnecessary detail.

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 tool's simplicity (two parameters, no output schema, no annotations), the description adequately conveys the core functionality. However, it lacks completeness in terms of error handling, prerequisites, and behavioral edge cases, which could be important for an agent to decide when to invoke this tool.

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 input schema describes both parameters (message and directory) with 100% coverage. The description adds no new information beyond what the schema provides, so the baseline of 3 applies. No additional semantic context like message formatting or directory constraints is provided.

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 performs a complete Git workflow of adding all changes, committing with a message, and pushing to remote. It specifies the verb ('add, commit, push'), the resource ('Git workflow'), and distinguishes itself from sibling tools which are individual git commands.

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 implies usage when a user wants to perform all three steps sequentially, but it does not explicitly state when to use this tool versus alternatives. There is no guidance on when not to use (e.g., if only one step is needed) or references to sibling tools like git-add, git-commit, or git-push.

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