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

Beyond the readOnly/idempotent annotations, the description discloses multiple behavioral traits: determinism, no login required, free usage ('Gratis (€0)'), and the return format ('righe strutturate ... + una resa testuale'). It also clarifies the non-official nature of the output, which is important context the annotations do not provide.

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?

Despite being long, the description is dense and well-structured: it starts with the core purpose, then covers the three modes with their codes and deadlines, the return type, the expected input chain, and finally the caveats. Every sentence adds valuable information and there is no 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?

Given the tool's three-mode complexity and the absence of an output schema, the description covers all modes concretely (codes, deadlines, split rules), states the output structure (structured rows + textual rendering), and identifies the exact upstream tools that produce the inputs. It also sets expectations about what it does not do, making the description complete for safe invocation.

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% with detailed per-field mappings to calc_* outputs, so the baseline is 3. The description adds high-level rules such as IMU split and bollo deferral, but most of the parameter-specific meanings are already in the schema, so the added semantic value is limited.

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 opens with a specific verb and resource: 'Compone le RIGHE del modello F24' (composes the rows of the F24 model), and enumerates the exact domains (Erario, INPS, IMU, bollo) and their codes. It clearly distinguishes itself from sibling calculators by stating it works 'a partire dagli importi già calcolati' (from already-calculated amounts).

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?

The description gives explicit when-to-use context by naming the typical input chain: 'l'input tipico sono gli output di calc_forfettario ... calc_imu ... parse_fatturapa'. It also provides an explicit exclusion: 'NON genera il modello ministeriale F24' and notes the result is an indicative compilation that does not substitute professional advice, offering clear boundaries for appropriate use.

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