save_snapshot

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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: this is a mutation that writes to git and commits only the design folder, and it requires explicit user intent. It omits whether the commit is reversible, what git state/prerequisites must exist, and what happens on failure, which is meaningful for an unannotated write tool.

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?

Two short sentences, zero filler. The core action and mechanism come first, and the gating condition follows immediately.

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 single-optional-parameter, no-output-schema tool, the description gives enough to decide when to call it and what it does. The only real gap is the undocumented 'message' parameter, which the schema also leaves bare.

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 parameter, 'message', with 0% schema description coverage, and the description never mentions it. An agent must infer that it is the git commit message and that it is optional (required list is empty); both facts are left unstated in prose.

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?

States a specific verb and resource ('Save a snapshot') and explains the mechanism: committing only the design folder to git, with a parenthetical gloss of what a snapshot is. No sibling tool overlaps with git save operations, so differentiation is not a problem, though it doesn't explicitly contrast with anything.

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?

Gives an explicit, restrictive usage condition: 'Use only when the user explicitly asks to save.' That is a strong when-to-use signal with a clear exclusion implied (don't save proactively). It does not name alternatives, but none of the listed siblings appear to be a fallback for saving.

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