Save the project

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

Annotations indicate this is a write operation (readOnlyHint=false), and the description confirms persistence behavior. It adds some context by distinguishing in-place overwrite from Save As, but it does not disclose details such as whether unsaved changes are silently discarded or how overwrite confirmation is handled.

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 one efficient sentence that front-loads the core action and then adds the only optional nuance. Every word 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?

For a one-parameter save operation with a complete schema, the description is largely sufficient. It would benefit from explicitly naming ae_save_frame as the alternative for frame output, but the tool is simple enough that this is a minor gap.

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 schema already documents the single 'path' parameter at 100% coverage, including its type and meaning. The description adds only slight semantic value by explaining 'Save As' and the in-place behavior, which is enough to meet the baseline but not exceed it.

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 clear, specific verb ('Save') and resource ('current project'), and immediately distinguishes the two modes: save in place versus Save As to a new path. This is unambiguous and separates it from siblings like ae_save_frame.

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 clarifies when to omit the path (save in place) and when to provide one (Save As), but it never explicitly says when to use this tool versus alternatives such as ae_save_frame or ae_export. Usage context is implied rather than stated.

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