project_save

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the user controls when saving happens, which is a useful behavioral trait. However, it does not disclose what happens during the save operation (e.g., whether it overwrites without confirmation, prompts for file path if unsaved, or fails silently if no project is open). This is a notable gap for a mutation-like 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 extremely concise: two sentences with no filler. The core action ('Save the current Audacity project') is front-loaded, and the usage guardrail follows immediately. Every sentence earns its place, making it easy to parse quickly.

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 zero-parameter tool with no output schema, the description covers the essential elements: what it does and when to call it. It does not mention error handling or return values, but these are often not critical for a simple save command. The description is sufficiently complete for an agent to use this tool correctly in most scenarios.

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 tool has zero parameters, so the description correctly adds no parameter-specific details. The baseline for 0 parameters is 4, and the description focuses on the tool's purpose and trigger condition rather than redundant parameter info, which is appropriate.

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 action: 'Save the current Audacity project.' It uses a specific verb and resource, and implicitly distinguishes from sibling save variants like project_save_as or raw_save by emphasizing 'current project'. An agent can tell exactly what this tool does without ambiguity.

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 explicit usage conditions: call 'ONLY when the user explicitly asks to save' and explicitly warns against auto-saving after effects or pipelines. This provides a clear guardrail and effectively differentiates when to use this tool versus not, without needing to name alternatives.

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