snapshot

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

With no annotations, the description carries the full disclosure burden and partially meets it: it explains that push triggers a network operation and that the default is off specifically to avoid a surprise network call. That rationale adds value beyond the schema's bare default:false. It stops short of disclosing whether the operation is reversible, what happens with an empty staging area, or any auth requirements.

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?

A single, front-loaded sentence with no filler; the key action comes first and the push caveat second. Only the parenthetical pathspec clause adds noise without corresponding schema support.

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?

An output schema exists, so return values need not be described, and the tool is low-complexity with only two parameters. Still, the description leaves the commit-message parameter undefined and asserts a pathspec concept that the schema does not support, so an agent cannot fully reconstruct intended usage from the definition alone.

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%, so the description must compensate for both parameters. It does explain the push flag's default behavior and rationale, but 'message' is never described even implicitly beyond its name. Half the parameters remain semantically unexplained.

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 a concrete action set (stage + commit, optional push) under the verb 'snapshot', which is more specific than a restatement of the name. However, it claims pathspec scoping through 'git add (pathspec-scoped)' while the input schema contains no pathspec parameter, which muddies rather than clarifies what the tool actually operates on. The 'git add + commit' framing does distinguish it from the graph-node siblings, but the pathspec mismatch creates ambiguity.

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?

There is no explicit when-to-use guidance or comparison to alternatives; the only contextual hint is the conditional nature of push. An agent is left to infer that this is the tool for persisting changes to a repo. No prerequisites, no statement of when not to use it.

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