it__build_pacchetto_versamento

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

No annotations are present, so the description is the only behavioral signal. It discloses what the tool creates, including the ZIP format and its contents, but it does not cover side effects, input validation behavior, error conditions, or whether the invoices must already be signed before calling.

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?

The description is two sentences with no wasted content. The primary action and artifact composition are front-loaded, and the domain context is provided in a single supporting sentence.

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?

The description is enough for selecting the tool but not for invoking it correctly. Without parameter semantics, especially for `documents_json` and `producer_id`, an agent cannot know what input structure to provide. The existence of an output schema does not compensate for missing input guidance.

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 input schema has 0% description coverage and the description does not explain either parameter. The agent cannot determine what `documents_json` should contain beyond what its name implies, and `producer_id` is completely unexplained.

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 starts with a specific verb and resource: 'Build a Pacchetto di Versamento (PdV) ZIP archive' and explicitly states what it contains — signed invoices and an XML index (IPdV). It distinguishes this from sibling tools like signing or archiving tools because it targets the AgID conservazione transfer artifact.

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 provides clear context: the PdV is the unit of transfer to an AgID-accredited conservazione provider, implying this tool is used when preparing such a transfer. It does not explicitly mention exclusions or alternatives, but the use case is sufficiently clear.

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