ilovevideoeditor_local_preview

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'Start or stop the local preview dev server.' It does not explain side effects (e.g., port usage, resource cleanup), what 'status' reports, or any requirements for starting. This is a significant gap for an operation that modifies local state.

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?

Two short sentences, front-loaded with the primary action. Every word earns its place. The description is concise and immediately readable.

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 dev server control tool, the description plus schema may be sufficient for basic use. However, there is no output schema and the description does not mention what 'status' returns or how the server lifecycle works. The ambiguity around 'file required for start' (not in required list) also leaves the agent with unanswered questions.

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 100%, so the schema already documents both parameters and the enum. The description adds the 'before capturing frames' context but repeats nothing new about parameter meanings. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 clearly states the tool starts or stops a local preview dev server, which is a specific verb+resource. It distinguishes itself from siblings by noting it is used before capturing frames, but it omits the 'status' action from the schema, so it is not fully complete.

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 phrase 'Use this before capturing frames' gives clear temporal context for when to invoke this tool relative to capture/analyze siblings. However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of a 5.

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