open_weather_forecast_israel

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

Discloses that the browser is visible (non-headless) and persistent for session reuse. No annotations, but description covers key behavioral aspects. Does not mention any potential side effects, but launch action is non-destructive.

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 paragraphs with clear front-loading of purpose. Could be slightly more concise, but no wasted sentences.

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 tool has no parameters and output schema likely describes return, description is complete. It covers the essential context: persistent session for reuse.

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?

No parameters; schema covers 100% of zero params. Description adds value by specifying the exact URL and browser mode, going beyond schema.

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 launches a persistent Chromium browser and opens a specific URL for Israel weather forecast. It distinguishes from sibling tools by indicating this is the setup step for subsequent tools to reuse the 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 to use before subsequent Israel weather tools. While no explicit when-not or alternatives, the context of sibling tools (enter, select, extract) implies this is the prerequisite opener.

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