save-project

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

With no annotations, the description carries full burden. It adds useful context: it targets the 'current' project and requires an 'absolute' path. However, it does not disclose that saving overwrites an existing file, whether the operation is reversible, or what happens on failure (e.g., invalid path, no open project). These are meaningful behavioral gaps for a mutation tool.

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 a single, well-constructed sentence with zero filler. The action and the critical path constraint are both front-loaded, making it easy to scan and immediately actionable.

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 simple one-parameter tool, the description covers the essential information: what is saved, the target, and the path format. It does not mention return values or error behavior, but given the simplicity and the absence of a sibling for saving, it is largely sufficient for an agent to invoke correctly.

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 0%, so the description must compensate. It does by specifying that the path must be 'absolute' and have the '.aep' extension, directly enriching the meaning of the single 'path' parameter. This goes beyond the bare schema and gives the agent the key constraints needed to call it correctly.

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 action ('Save') on a specific resource ('current AE project') with a specific destination ('absolute .aep path'). This is unambiguous and clearly distinct from all sibling tools, none of which involve saving projects.

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 purpose is so self-evident that usage is implied, but the description gives no explicit when-to-use conditions or alternatives. It does not mention prerequisites like an open project, or contrast with any other save-like action, so it relies on the agent inferring the obvious use case.

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