td_snapshot

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

With no annotations, the description carries the behavioral burden. It clearly discloses the file destination (~/.td-atlas/snapshots) and explains that a component is written rather than the session, avoiding a subtle Save As side effect. It does not cover overwrite or naming behavior, but the key side effects are 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?

Three short paragraphs, each with a distinct job: purpose, usage pattern, and rationale. The most important information is front-loaded, and there is no 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?

The workflow and file location are covered, and the existing output schema means return values need not be described. However, with no annotations and no parameter explanation, the exact role of path and label remains a meaningful gap for confident invocation.

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%, and the description never explains what 'path' or 'label' mean or how they affect the snapshot. The defaults give hints, but the description adds no direct parameter guidance.

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 names a precise verb and resource: 'Save a component to a file'. It also states the intended purpose ('so it can be diffed later') and explicitly connects to td_project_diff, distinguishing it from sibling tools.

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?

It gives an explicit workflow: take a snapshot before edits, another after, then pass both to td_project_diff. It also explains why saving the whole session is inappropriate, providing a clear boundary for when to use this tool.

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