JIZURAを開く

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

With no annotations, the description must carry the behavioral burden. It discloses the browser engine (Playwright Chromium) and that the call establishes a stateful, manipulable session, which is meaningful. However it omits whether calling it twice is safe, whether the session must be cleaned up via jizura_close, and any failure/rate-limit behavior — notable gaps for a state-establishing tool.

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 with zero filler: the action/URL comes first, the prerequisite-ordering rule second. Nothing could be removed without losing information.

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?

No output schema and no annotations, but for a session-opener the description covers what the agent needs: what is opened, how, and when to call it. Minor gap: the session lifecycle (repeated calls, cleanup via jizura_close) is left to inference from sibling names.

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?

There is only one parameter (headless) and the schema documents it at 100% coverage, including the default (false = visible window). The description adds nothing about it, so the baseline of 3 applies.

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 ('開き' / open) plus the exact target resource (the JIZURA URL loaded via Playwright Chromium) and the effect ('操作可能なセッションを開始する'). This clearly separates it from the action siblings (click, fill, snapshot), which operate on an already-open session.

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?

Explicitly states the prerequisite ordering: '他のjizura_*ツールを使う前に一度呼ぶ' (call once before using the other jizura_* tools). It does not state any when-not condition or mention jizura_close as the lifecycle counterpart, but the invocation context is unambiguous.

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