Save project

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 states the core action (saving to disk) but does not mention important side effects like overwriting behavior, whether a project must be open, or if any dialog is shown. While minimal, it conveys the essential behavior; however, it lacks depth about potential failure modes or confirmation prompts.

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, clear sentence that front-loads the action and resource. It contains no filler or unnecessary detail, earning every word. Perfectly structured for rapid parsing by an agent.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is complete. It fully communicates what the tool does without needing additional context about return values or edge cases. An agent can confidently invoke this tool based on the description alone.

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, and the schema is an empty object with 100% coverage. As there are no parameters to describe, the baseline of 4 applies. The description adds the semantic that it operates on the 'current' project, which is a useful implicit constraint that isn't in the schema.

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 'Save the current REAPER project to disk' states a specific verb (save), a clear resource (current REAPER project), and the target (disk). It is unambiguous and distinguishes itself from sibling tools, none of which perform a save operation.

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?

No guidance is given on when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. The usage is implied by the name and description, but there is no explicit context such as 'use this after making changes' or 'cannot be undone'. This is adequate for a trivial operation but leaves the agent to infer appropriateness.

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