end_audition

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

Annotations already declare this is a non-read-only, idempotent, non-destructive mutation, so the safety profile is covered. The description adds the key post-condition, that the stored preset is restored, which hints that unsaved audition tweaks are discarded, but it never says so explicitly or describes error behavior outside audition mode.

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?

A single short sentence with the action front-loaded and no filler. Nothing is wasted and the resulting state follows immediately after the verb.

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, no-output-schema toggle, the description covers what an agent needs to invoke it. The remaining gap is whether in-progress audition edits are lost on exit, which matters for an agent deciding whether to save first.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are present.

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?

States a specific verb and resource: leave audition mode, and adds the resulting state (return to the stored preset). An agent can tell it apart from preset-mutating siblings such as save_preset or select_preset, though the complementary sibling audition_preset is never named, so the pairing is left implicit.

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?

Usage is only implied: an agent infers it should call this to exit the audition state, presumably after audition_preset. There is no explicit statement of when to use it, no note about what happens if the tool is called when not in audition mode, and no named alternative.

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