td_project_lifecycle

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description lists mutating actions (save, undo, redo) but adds no extra behavioral context such as what gets destroyed, whether files are overwritten, or the undo stack behavior. The description does not contradict annotations.

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, short sentence that lists the key actions. It is concise and front-loaded with the main purpose, but lacks structure (e.g., bullet points or separate sentences for each action). Every word is earned, but the terseness limits informativeness.

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?

Despite having an output schema (not shown) and 100% parameter coverage, the description fails to explain the effects of each action, the undo/redo block mechanism, or prerequisites like an open project. For a tool with 5 parameters and multiple modes, this is insufficient.

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 coverage is 100% and each parameter has a clear description. The tool description adds no additional parameter information, so it meets the baseline for high coverage without adding extra value.

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 clearly states the tool handles save/load/undo/redo operations for project lifecycle, which is specific enough to distinguish from most sibling tools like td_snapshot_scene or td_get_state_vector. However, it could be more precise by naming the resource (project file) and listing actions more formally.

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?

No guidance on when to use this tool versus alternatives like td_snapshot_scene or td_restore_snapshot. The description does not mention prerequisites, context, or exclusions. The agent must infer usage from the action list alone.

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