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

Annotations already declare idempotentHint, destructiveHint=false and readOnlyHint=false; the description adds genuinely new behavior: same-slug entries overwrite rather than duplicate, nothing is ever deleted, and it returns a count of saved sheets (useful since there is no output schema). It does not mention permissions or failure modes, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the operation and limits, then format source, then content constraints, then return value. Every sentence 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 non-destructive upsert with full annotation coverage, the description supplies the missing pieces: batch limit, format source, content rules, and the return count that stands in for the absent output schema. Only auth/permission expectations and error behavior are unstated.

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 parameter's description already explains the 1-50 range and same-slug update semantics. The description largely restates this and adds only the pointer to formato_schede, so the schema is doing the heavy lifting.

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 pair (inserisce/aggiorna) plus the resource (schede progetto), the keying mechanism (per slug) and the batch cap (fino a 50). This is clearly distinguishable from sibling portfolio_elenco, which only lists.

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?

Routes the agent to the sibling formato_schede for format and allowed values, and rules out a class of content ('solo fatti trovati nei file, niente segreti né codice'). It also clarifies the operation is an upsert, not a delete. It stops short of an explicit when-not-to-use statement, but the context is clear.

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