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

Beyond the readOnly/idempotent annotations, the description discloses meaningful behavior: the link does not create orders, document and acceptance remain the client's, coverage may be rejected for a given address, and the attested street mismatch is surfaced in `interpretazione`. It also explains the number-confirmation flow (SMS link or code). Rich behavioral context, though it doesn't describe the link's lifetime 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?

The purpose is front-loaded and each sentence carries substantive constraints (mandatory cliente, address behavior, no-order guarantee, confirmation flow). It is a dense, somewhat long paragraph but nearly every clause earns its place; no filler or restated annotations.

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 an 8-parameter, no-output-schema read tool with annotations already covering safety, the description covers the key behavioral and parameter aspects and even names the `interpretazione` field. It is largely sufficient for correct invocation, with only peripheral params (cap, provincia, agente) left unexplained.

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?

With schema coverage at 50%, the description compensates by explaining the cliente enum's business meaning, the role of comune/via/civico in coverage rechecking, and the interpretation output when the verified street differs. It adds meaning for the address trio and cliente beyond the schema, though cap, provincia, and agente remain unaddressed in both places.

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 opening states a specific verb and resource: "Restituisce il link alla pagina di sottoscrizione di un'offerta, con indirizzo e tecnologia già compilati." An agent can tell it produces a subscription link rather than merely checking coverage. It does not explicitly name or differentiate from siblings such as verifica_copertura or dettaglio_offerta, so it falls short of a 5.

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?

Usage is implied through preconditions (cliente is obbligatorio, business vs private rules, address needed for technology in the link) rather than stated as when-to-use vs alternatives. No explicit routing to verifica_copertura or other siblings is given, even though coverage is recheckable here. Adequate but with clear gaps.

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