Autocompleta Stazione Nts

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

With no annotations, the description carries the full burden. It usefully discloses the code format (9-11 digits, prefix 83) and an interoperability constraint, but says nothing about whether the lookup is read-only, how many matches are returned, or what the output schema contains. It adds real context but leaves the behavioral profile thin.

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 tight sentences with the core purpose front-loaded and the code-format detail in a parenthetical. No filler, though the domain examples (BIVIO, DEV., PC) are somewhat dense for an English-reading agent.

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?

An output schema exists, so return-value explanation is not needed. For a single-parameter autocomplete tool, the description covers what it searches and the key interop caveat. Only the prefix parameter's expected format remains under-specified.

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?

One required parameter (prefisso) with 0% schema description coverage, so the description must compensate. 'Autocompletamento' implies prefix-matching semantics, but the description never states what prefisso should contain (code prefix vs. name fragment) or matching rules. Marginal value over the bare 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?

States a specific verb (autocompletamento) and a well-scoped resource (stazioni e nodi tecnici ferroviari: bivi, deviazioni, posti di comunicazione) and pins the output to 9-11 digit RICS codes starting with 83. This clearly distinguishes it from the sibling autocompleta_stazione, which handles ordinary stations.

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 note that these NTS codes 'non vanno usati con gli altri endpoint ordinari' gives a when-not caveat, but it is about downstream usage of the returned codes, not about when to select this tool over autocompleta_stazione or cerca_stazione. Usage context is implied by the domain rather than explicitly routed.

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