ae_save_project

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 usefully discloses the two distinct write modes, but a save operation's most important trait — that it overwrites the target file, and what happens on an invalid or non-absolute path — is not mentioned, nor are any return or error signals.

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?

Two compact sentences, the primary action front-loaded and the branching behavior immediately after. Every clause carries information; there is no filler or restated title.

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 persistence tool with no annotations and no output schema, the description covers the essential decision an agent must make. It is slightly incomplete on failure behavior and overwrite semantics, which matters for a save-as write, but nothing critical to correct invocation is missing.

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 parameter is already documented as "Optional absolute .aep path", so the baseline would be 3. The description earns an extra point by explaining the consequence of supplying versus omitting the parameter, which the schema alone 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?

Specific verb+resource ("Save the open project") with the two operating modes spelled out, including the Save As variant. No sibling tool in the set performs saving, so there is no ambiguity to resolve, and the agent can tell instantly that this is a project-persistence call rather than a creation or open call.

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 gives the condition that selects each behavior: no path means save in place, an absolute .aep path means Save As. It stops short of naming alternatives or stating exclusions (e.g., what to do for a first-time save of an unsaved project), so it is clear context rather than full routing guidance.

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