saveProject

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the two write modes and that saving targets an .aep file, but it omits overwrite semantics for an existing saveAsPath, permission/error behavior, and whether the operation returns the written path.

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?

One sentence, zero padding, with the primary action front-loaded and the alternative mode stated immediately after. Every clause carries information.

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, zero-annotation tool with no output schema, the description covers both execution modes adequately. It is slightly thin on post-save behavior (return value, failure modes) that an agent might want given the absence of an output schema.

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 the single optional parameter is fully documented in the schema. The description echoes 'new file path' and adds that it produces a .aep copy, but adds no syntax, absolute-path requirement, or overwrite rule beyond the schema baseline.

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 uses a specific verb+resource ('Save the current After Effects project file') and distinguishes two distinct modes: in-place save versus save-as to a new path. It is unambiguous, though it does not explicitly contrast itself with any sibling tool (no other save tool exists among the siblings).

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?

Usage is implied by the phrasing: omit the path to overwrite the current project, supply 'saveAsPath' to write a copy. There is no explicit statement of preconditions (e.g. a project must be open) or when-not-to-use guidance, so the agent must infer the branch condition.

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