raw_zoom_normal

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

No annotations are provided, so the description carries the full burden. It does add useful caution: 'May open a dialog or change project state.' However, this is vague and does not specify what dialog or which project-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 first sentence is concise and front-loaded. The second sentence adds a useful caveat, but 'inspect the command name first' is unclear and somewhat redundant, reducing overall crispness.

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 simple no-argument zoom-reset action, the description covers the basic function and warns about possible side effects. Still, it lacks details about when to choose this tool over other zoom commands and what 'change project state' means in practice.

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 already fully represents that with empty properties. The description reinforces 'no-argument' but adds no meaningful parameter semantics. Baseline 4 is appropriate for a zero-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 a specific verb and resource: 'Reset zoom to the default view.' This clearly distinguishes it from sibling zoom tools like raw_zoom_in, raw_zoom_out, raw_zoom_sel, and raw_zoom_toggle. The core action and target state are immediately understandable.

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 for when to use this tool over its zoom siblings. It does not mention alternatives or conditions such as 'use raw_zoom_out to zoom away from default.' The phrase 'inspect the command name first' is not a real usage guideline.

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