project_snapshot

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 mentions 'timestamped' and 'collision-free,' which implies it creates uniquely named backups, but it does not disclose side effects, required permissions, whether it overwrites existing files, or what happens on failure. The description is minimal and leaves the agent to infer important behavioral details.

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 and well-structured. The first sentence states the primary purpose, and the second line provides the only parameter's explanation. There is no redundant filler, and the essential information is front-loaded.

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 simplicity of this tool (one optional parameter, no output schema, no annotations), the description covers the core information: what it does and where the backup goes. It does not specify return values or error handling, but for a single-purpose backup tool, these may not be critical. The description is sufficient for an agent to invoke it correctly in most scenarios.

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?

The description adds meaningful parameter semantics beyond the schema. The schema only lists 'dest' with anyOf string/null and a default null, but the description explains that 'dest' is the backup folder and defaults to 'snapshots/' next to the project. This clarifies the null behavior and default location, which the schema does not convey.

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 verb and resource: 'Save a timestamped, collision-free backup .toe.' This clearly indicates the tool creates a backup of a TouchDesigner project file. While it doesn't explicitly differentiate from sibling tools like node_snapshot or bridge_snapshot, the name 'project_snapshot' and the focus on a .toe file make the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives or any prerequisites. It only states what it does and the parameter default. There is no mention of scenarios where another snapshot tool would be more appropriate, nor any exclusions or context for usage.

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