raw_save_compressed

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose that this is a 'static no-argument Audacity action' and warns that it 'may open a dialog or change project state.' This is useful risk signaling, though the phrasing is hedged and does not specify which dialog or state changes could occur.

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 short, front-loaded with the core purpose, and each sentence earns its place. The final instruction to 'inspect the command name first' is somewhat vague and detracts slightly, but overall the structure is efficient.

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 raw Audacity action, the description covers the action, argument count, and a risk warning. However, it does not explain the return behavior, clarify what state changes are possible, or position itself among the many sibling save/project tools, so it is not fully complete for safe autonomous selection.

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 schema has zero parameters and the description explicitly confirms 'no-argument.' With no parameters to document, the description need not add more; the baseline of 4 is appropriate and the mention of being no-argument reinforces 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 states a clear verb and resource: 'Save a compressed copy of the project.' The word 'compressed' meaningfully distinguishes it from close siblings such as raw_save, raw_save_as, and raw_save_copy. An agent can tell what this tool does without opening a schema.

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 safety advice ('May open a dialog or change project state; inspect the command name first') but does not say when to use SaveCompressed versus alternative save/copy actions. There are no conditions, exclusions, or explicit routing to sibling tools, so the agent is left without selection guidance.

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