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

Annotations already flag a non-readonly, non-idempotent, open-world write; the description goes well beyond them by disclosing the one-time 30-minute upload link, the required build layout, the zip + curl upload flow, and a pre-publish quality checklist. It also clarifies the consent gate, which is the main failure mode callers will hit.

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?

Purpose is front-loaded in the first clause, and the remaining sentences each carry distinct operational content (gating condition, return contract, build steps, quality check). It is dense and slightly run-on, but nothing is filler.

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?

Although there is no output schema, the description spells out the return value (link monouso + istruzioni) and the full downstream procedure, and adds the quality-review requirement. Combined with one-parameter schema coverage, an agent has everything needed to invoke it correctly.

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 coverage is 100% and the single id parameter is already documented as 'id del cantiere' in the schema. The description refers to the cantiere throughout but adds no new syntax, format, or sourcing detail for the id, so the baseline 3 applies.

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 and resource in one clause: mette online la demo statica di un cantiere sullo spazio demo di DeviL. The workflow context (destinazione DeviL, consenso, pulsante «Pubblica la demo») clearly separates it from the other *_salva and metti_in_coda siblings.

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?

Explicit preconditions are given (selezionato lo spazio DeviL, consenso, pulsante premuto) plus where to find the trigger (DEMO DA PUBBLICARE in cantieri_da_lavorare) and the fallback behaviour (altrimenti spiega cosa fare). This is exactly the when-to-use vs. when-not guidance an agent needs.

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