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. It discloses the critical behavioral constraint that this is a manual-only operation (not to be called automatically after effects/pipelines). It implies mutation of the current project file but does not mention error states, idempotency, or return values.

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?

Three sentences with zero waste: first establishes purpose, second states positive constraint, third states negative constraint. Information is front-loaded and each sentence earns its place by preventing common misuse patterns (auto-saving).

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 save operation without output schema or annotations, the description is complete. It covers purpose, explicit user intent requirements, and anti-patterns (auto-save). No critical information is missing for correct invocation.

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 input schema contains 0 parameters, establishing a baseline of 4. The description requires no parameter clarification, and the 'current Audacity project' phrasing correctly implies the target resource is implicit rather than passed as an argument.

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 the specific action ('Save') and resource ('current Audacity project'), clearly distinguishing it from siblings like project_save_as, project_open, and project_close. The scope is immediately clear.

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?

Provides explicit when-to-use ('ONLY call this when the user explicitly asks to save') and when-not-to-use ('Do NOT auto-save after effects or pipelines') guidance. The prohibition against auto-saving after effects directly references sibling effect tools and prevents incorrect invocation patterns.

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