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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description adds meaningful context beyond them: it 'takes at most one at a time' (explaining the non-read-only, non-idempotent nature), inspects git history per folder for unaligned commits, and can trigger an external call to aggiorna_cantiere (esterno: true). It still leaves the exact state effect ambiguous (whether the consumed cantiere is removed, marked, or merely read), which is the only real gap.

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?

It is front-loaded with the tool's purpose before branching into the new / to-continue / active-alignment cases, which is the right ordering. The sentences are long and heavily embedded, but each one carries distinct information about a separate behavior, so little is wasted.

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?

With no output schema, the description carries the full burden of explaining returns and it does so concretely for each case (brief to save as CLAUDE.md, folder + user indications + next stage, unaligned commits). It is complete enough for an agent to act, though the side effect of consuming queue items and the relationship to sibling queue tools remain implicit.

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?

The tool takes zero parameters, so the baseline of 4 applies. Nothing in the description needs to document inputs, and it correctly spends its text on outputs and behavior instead.

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 states a specific verb+resource: it pulls queued development 'cantieri' from DeviL and returns either the brief (new) or folder/instructions/next stage (to continue). It is clear about what the tool does, but it never differentiates itself from similarly named siblings such as dossier_da_lavorare or metti_in_coda, leaving the agent to infer which queue-feeding tool is which.

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 the two branches (new vs to-continue) and the mention of calling aggiorna_cantiere to report commits, which is a routing hint. However, there is no explicit statement of when to prefer this tool over siblings like dossier_da_lavorare, nor any when-not guidance or prerequisite conditions.

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