enter_weather_forecast_city_israel

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

With no annotations, the description carries the full burden. It discloses that the tool returns autocomplete suggestions numbered from 0, may include non-city results, and provides a concrete example ("חיפה" yielding "חוף הסטודנטים, חיפה" first). This is rich, actionable 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?

Three succinct sentences cover the action, return behavior, and next step, plus a clear Args section. Every sentence earns its place; no fluff or redundancy.

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 one-parameter tool with an output schema (not shown), the description covers the action, return semantics, caveats, and the follow-up call. It is fully complete for guiding correct tool invocation within the sibling workflow.

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 only defines 'city' as a string with no description. The description adds that the city name must be in Hebrew and provides examples (תל אביב, חיפה, באר שבע), which is critical for correct input and goes well beyond the 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 states a specific action ('Type an Israeli city name into the forecast search box') with a clear verb and resource. It distinguishes from siblings by describing the initial entry step, leaving selection to select_weather_forecast_city_israel.

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 instructs to 'Read the list before choosing, then call select_weather_forecast_city_israel', defining the workflow and when to use this tool. It also warns about neighbourhoods and landmarks, helping the agent interpret results correctly.

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