zoom_editor

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Zoom' without explaining side effects, how zoom_level is interpreted, whether a scene must be loaded, or if the change is persistent. This is entirely opaque.

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 one short sentence with no extraneous words, making it very concise and front-loaded. However, it is so brief that it borders on under-specification, which is more of a completeness issue than a conciseness problem.

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 tool with one parameter, a one-line description could suffice if it explained the key parameter semantics. Here, the critical zoom_level value is completely undocumented, and there is no mention of return values or side effects, making the description incomplete for correct invocation.

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 defines zoom_level as a number with no description (0% coverage). The description does not mention the parameter at all, so it fails to clarify what value to provide (e.g., 1.0 = normal, 2.0 = zoom in). This is a critical omission.

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 action ('Zoom') and resource ('the Godot 2D editor'), which clearly distinguishes it from sibling tools like get_editor_status or create_scene. However, it does not clarify whether it sets an absolute zoom level or zooms in/out incrementally, so it is not maximally precise.

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 provided on when to use this tool versus alternatives, nor any prerequisites such as the editor needing to be open. The only hint is the verb 'Zoom,' which is too minimal to count as meaningful usage guidance.

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