ilovevideoeditor_local_capture

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

No annotations are provided, so the description must disclose behavior. It does not state whether the screenshot is returned as data or saved, nor does it mention any side effects or permission requirements. Additionally, 'at a given time' implies the time parameter is required, but the schema marks it optional, which is a minor inconsistency with the behavioral context.

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 a single, focused sentence with no unnecessary words. It is well-structured and front-loaded with the action.

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 tool with no output schema and no annotations, the description leaves important gaps: it does not specify the return format of the screenshot or what 'given time' means if omitted. It also does not explain how the local preview is accessed or what happens if it isn't running, making it incomplete for an agent to invoke confidently.

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 already provides descriptions for both parameters, and the description adds little beyond the phrase 'at a given time.' Format and default behavior are covered by the schema, so the description adds marginal value.

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 it captures a screenshot from the running local preview at a given time, which is a specific verb and resource. It distinguishes this tool from siblings like render or analyze by focusing on screenshot capture from the local preview.

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 description implies a use case—capturing a screenshot from the running local preview—but does not explicitly contrast it with alternatives or state when not to use it. The mention of 'running local preview' signals a prerequisite, but no explicit guidance is given.

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