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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-destructive but state-affecting call. The description adds real context (what the downloaded README contains, empty-queue outcome) but never says what the call mutates — i.e. whether the queue items are consumed/marked as taken — which matters given readOnlyHint=false and idempotentHint=false and would affect retry decisions.

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?

Front-loaded with the core action and the payload, then the workflow step, then the special-case parameter value. It is dense and a little run-on with nested parentheticals, but every clause (README contents, invia_risultati, top: 0, empty queue) carries information an agent needs.

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 one-parameter tool with no output schema, the description covers the trigger, the follow-up tool, the top: 0 mode, and the empty-queue outcome. The only real gap is the side-effect/state semantics flagged above, which is not fully resolvable from the description alone.

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 100% and the single parameter already documents 'oltre alla coda, quante aziende migliori non ancora analizzate aggiungere (0 = solo la coda)'. The description restates the top > 0 case and adds the top: 0 operating scenario, which is marginal added meaning over the schema — the baseline 3 is appropriate.

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 (scarica) and resource (i dossier delle aziende in coda), plus the exact payload contents (README, regole di scrittura, catalogo, verifica date, ricerca in rete, formato risultati). It also positions itself in the workflow by naming the follow-up sibling invia_risultati, so an agent can separate this from the send step without opening either schema.

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 routing: use invia_risultati afterwards to send results, use top: 0 when only the queue should be worked (the /loop and 'Manda al mio Claude Code' cases are named concretely). It even covers the degenerate case — 'se la coda è vuota non c'è niente da fare' — which is exactly the kind of when-not guidance that prevents wasted calls.

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