save_changes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly reveals the side effects: staging all changes, committing, and pushing to origin/main. It also communicates the approval gate. It does not mention remote/auth failure modes or irreversibility, but the core behavior is transparently stated.

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: three short sentences that front-load the action and then give the critical usage constraint. Every sentence earns its place, and there is no redundant filler.

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 simple one-parameter tool, the description covers the action and the approval condition well. However, the lone optional parameter is undocumented, and with no output schema, the agent is left guessing about return values or default behavior when message is null. These gaps prevent full completeness.

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?

There is one optional 'message' parameter with 0% schema coverage, and the description never explains it. An agent can only infer that 'message' is the commit message from the word 'commit'; the description does not state whether it is required, what happens when omitted, or how it is used. With low schema coverage, the description needed to compensate and did not.

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 opens with a specific verb and resource: 'Stage all changes, commit, push origin main.' This unambiguously identifies the tool as a git save-and-push operation and clearly distinguishes it from sibling tools focused on notes, projects, and pending-change listing.

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 an explicit condition: 'ONLY call this tool when the user has explicitly approved the change' and provides concrete examples ('save it', 'commit that', 'looks good, push it'). It also states a clear exclusion: drafts iterated without approval should remain uncommitted.

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