git_snapshot

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

Even though annotations already mark destructiveHint:true, the description adds valuable behavioral detail: confirm commits only the vault pathspec, leaves outside files untouched, never pushes, and blocks on validation errors or Git operations in progress. It also explains the dry-run return contract and expectedHead requirement, giving the agent meaningful insight beyond the annotation flags.

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 compact and front-loaded, with the core purpose in the first sentence. The second sentence packs many safety clauses, but its run-on grammar and list-like structure ('requires that expectedHead, blocks validator errors...') make it slightly harder to parse. Still, no filler is present and every clause earns its place.

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 complexity, an output schema exists, and annotations already flags destructive behavior, the description provides enough context for safe invocation: dry-run flow, confirm semantics, expectedHead, vault-only commits, and no push. It doesn't describe exact return structure, but that is covered by the output schema, and it omits no critical invocation step.

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 100%, so the baseline is 3. The description clarifies the interaction between confirm and expectedHead and mentions the deterministic auto-generated message, adding some cross-parameter meaning. However, it does not go deeply beyond what the schema already says; the schema itself already documents the dry-run-first confirm requirement and the expectedHead copy instruction.

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 specific action ('Create a local, vault-scoped Git checkpoint') and clearly distinguishes it from sibling tools by emphasizing local, vault-scoped, and 'never pushes.' An agent can tell git_snapshot apart from git_status or git_history because the purpose includes scope, local-only behavior, and checkpoint creation.

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 clear workflow guidance: dry-run by default, review the returned preview/risk fields, then set confirm:true. It also states behavioral preconditions such as blocking on validator errors and active Git operations. It does not explicitly name alternative tools or say 'use X instead', which keeps this from a 5, but the usage context is unmistakable.

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