enter_weather_forecast_city_israel

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

Discloses that suggestions are numbered from 0 and may include non-city entries. However, without annotations, it lacks explicit statement of read-only nature, auth requirements, or rate limits.

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?

Four sentences, front-loaded with action. Each sentence adds value: action, result, caveat, instructions. No fluff.

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 simple single-parameter tool with output schema, description fully covers purpose, behavior, and next steps. References sibling tool to complete 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?

Parameter 'city' has only a type in schema (0% coverage). Description adds required format: Hebrew city name with concrete examples, which is essential for correct usage.

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?

Clearly states the action 'Type an Israeli city name' and the result 'Returns the autocomplete suggestions'. Distinguishes from sibling select_weather_forecast_city_israel by prescribing next step.

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 selecting and calls the sibling tool. Provides context that suggestions may include neighbourhoods and landmarks, helping agent make informed choice.

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