raw_zoom_out

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

With no annotations, the description carries the full burden of behavioral disclosure. It warns that the action 'may open a dialog or change project state' and clarifies the call is static and no-argument, which is valuable. It could say more about what state changes or dialog may occur, but it is reasonably transparent for a simple action.

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 compact and front-loaded, stating the action first and then adding a caution about side effects. The leading 'ZoomOut:' label echoes the tool name, but the overall text is short and focused.

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 no-parameter tool with no output schema, the description covers purpose, scope, and a warning about possible dialogs or state changes. The instruction to 'inspect the command name first' is vague, and success/error behavior is not described, but these are minor gaps at this low complexity level.

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?

There are zero parameters and the schema already shows an empty properties object, so there is nothing missing. The description reinforces this with 'no-argument', which meets the baseline for a no-parameter tool.

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 exact action: 'Zoom out horizontally', which is a specific verb plus resource and distinguishes this from zoom-in or zoom-normal siblings. It also identifies it as a 'Static no-argument Audacity action', but it does not explicitly compare against related zoom commands.

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 implies when to use the tool: when a horizontal zoom-out is needed without arguments. However, it gives no explicit when-not-to-use guidance and does not name alternative sibling tools, so the usage guidance is more implied than stated.

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