filmora_zoom

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

Annotations already carry the safety profile (readOnlyHint=false, openWorldHint=false, destructiveHint=true). The description adds real context by disclosing that this works via Filmora's default keyboard shortcuts, which implies focus/modifier-state dependence. However, it never explains why a zoom is flagged destructive, nor whether it depends on the active window, so a notable gap remains.

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 front-loaded sentence with no filler or redundancy. It is efficient, though for a tool carrying a destructive hint the brevity tips into under-specification rather than tightness.

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?

With only two parameters and no output schema, little is required, but the destructiveHint=true annotation is left completely unreconciled by a description that sounds like a harmless view change. An agent cannot tell what, if anything, gets altered or destroyed, or what prerequisite state is needed.

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?

Schema description coverage is 0% and the description supplies no parameter meaning at all. Direction's enum (in/out/fit) is self-explanatory from the schema, but 'repeat' is only described by its title and default, with no explanation of what is repeated or at what increments.

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 (zoom) and resource (the timeline), so the operator is unambiguous. It does not differentiate itself from overlapping view/shortcut siblings like filmora_key, filmora_playback or filmora_ui_action, but the purpose itself is clear.

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?

There is no guidance on when to reach for this tool versus sibling input tools (filmora_key, filmora_scroll, filmora_command) or when not to use it. The mention of 'default shortcuts' hints at mechanism but not at the conditions for use.

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