select_weather_forecast_city_israel

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

Description reveals the clicking action and page loading. Warns about index behavior. No annotations provided, so description carries full burden. Does not detail error handling or outcomes, but adequate for this simple 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 concise sentences plus Args section. Front-loaded with action. No unnecessary 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?

Description covers tool purpose and parameter usage. Output schema exists but return values are not described, which is acceptable per rules. Adequate for agent to select and invoke 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?

Schema has 0% coverage, but description explains 'index' as suggestion number starting from 0, with guidance to prefer text-match. Adds significant meaning beyond type and default.

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 states 'Click a city from the autocomplete list and load its forecast page,' clearly identifying the action and resource. It distinguishes from siblings like 'enter_weather_forecast_city_israel' (typing) and 'open_weather_forecast_israel' (opening page).

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?

Provides explicit guidance: prefers index matching the city text, warns that first item may not be correct. Implies use after entering text. Lacks explicit when-not-to-use statements but context from siblings fills the gap.

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