raw_zoom_toggle

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

With no annotations provided, the description carries the full burden and does disclose that the tool 'may open a dialog or change project state'. This is useful behavioral context beyond the stated toggle action, though it remains vague about exactly when these side effects 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 and front-loaded, with no wasted words. The 'ZoomToggle:' prefix is slightly redundant with the tool name, and 'inspect the command name first' is vague, but the overall 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, no-output tool, the description is mostly complete: it explains what the action does, that it takes no arguments, and that it may have side effects. It could define the 'two preset zoom levels' or clarify how to inspect the command name, but the low complexity keeps the gap minor.

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 is empty and schema description coverage is high, so no parameter details are needed. The description adds the relevant fact that this is a 'no-argument' action, which appropriately confirms the static nature of the 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?

States a specific action: toggling between two preset zoom levels, which goes well beyond the raw tool name. It distinguishes itself from zoom_in/zoom_out by describing a toggle behavior, though it does not explicitly differentiate from the generic raw_toggle sibling.

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 no guidance on when to use this tool versus alternatives like raw_zoom_in, raw_zoom_out, or raw_zoom_normal. The phrase 'inspect the command name first' is a caution, not a usage condition, and no when/when-not guidance is supplied.

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