Trova la zona del bollettino valanghe

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

Annotations already declare readOnlyHint=true, so the description's burden is reduced. It adds behavioral context by stating that the output is the EAWS zone to be used with the avalanche bulletin, and that the tool is a prerequisite step. It doesn't cover edge cases like points outside bulletin areas, but annotations mitigate the need.

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 sentences, both dense with information. The first states the core function; the second provides immediate actionable usage advice. No fluff or repetition.

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 two-coordinate lookup tool with an output schema, the description covers the essential purpose and usage guidance. Minor omission is handling of points outside any avalanche bulletin zone, but the read-only annotation and output schema likely fill that gap.

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 description coverage is 0%: the properties lat/lon have only numeric ranges, no descriptions. The description only says 'Dato un punto', which implies a coordinate pair but fails to specify decimal-degree format, coordinate system, or how lat/lon map to the two parameters. This leaves too much for the agent to infer.

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 opens with 'Dato un punto, individua la micro-regione EAWS a cui appartiene', using a specific verb (individua) and a specific resource (micro-regione EAWS). It also explicitly ties the tool to `bollettino_valanghe`, making its role clear and distinguishing it from sibling tools like `cerca_localita`.

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?

The description gives an explicit directive: 'Usa questo tool prima di bollettino_valanghe invece di indovinare l'identificativo della zona.' This tells the agent exactly when to use the tool and what alternative to avoid.

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