timelapse_start

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that execution is background and returns immediately, and provides operational guidance such as autofocus recommendation at night and auto-exposure behavior. It does not mention side effects like job creation or permission requirements, but covers the most relevant behavioral traits.

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 well-structured with a concise opening sentence followed by a clear bullet list. Each bullet explains one parameter with relevant context, and no sentence is wasted. It is appropriately sized for a 10-parameter tool.

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?

Given the tool's complexity (10 parameters, no annotations, output schema exists), the description is remarkably complete. It covers all parameters, default behaviors, lifecycle aspects (stop to end), and practical recommendations, leaving no significant gaps for an agent to operate correctly.

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 schema has 0% description coverage, so the description fully compensates by explaining every parameter in detail: what values mean, examples, defaults, and recommendations (e.g., autofocus false at night, ae_target for silhouette). This is exemplary parameter documentation.

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 action ('タイムラプス撮影ジョブを開始する' – start a timelapse capture job) and differentiates it from sibling tools like timelapse_stop, timelapse_status, and timelapse_list. It also highlights the background execution and immediate return, further distinguishing its behavior.

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 provides clear context for when to use the tool (starting a timelapse job) and explains key behaviors like immediate return and background execution. However, it does not explicitly mention when not to use it or offer alternatives, though the sibling names make this somewhat implicit.

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