It Sign Fattura Cades

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

With no annotations provided, the description carries the full burden and does it well. It discloses the DER-encoded base64 output, the signer microservice fallback behavior, the qualified PKCS#12 requirement, and the irreversible/confirmation requirement.

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 sentences, all substantive, with the core action and output front-loaded. There is no filler, and each sentence adds a distinct piece of information: purpose, output, prerequisite, fallback behavior, and irreversibility.

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 output schema presumably covers the return contract, and the description covers output encoding, prerequisites, and the irreversible confirmation flow. The only notable gap is clarifying when the optional cert_path/cert_password parameters are actually needed, given the microservice fallback, but the description is otherwise complete for a signing tool.

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 0%, so the description must compensate. It mentions a qualified PKCS#12 certificate (mapping loosely to cert_path/cert_password) and confirmation (mapping to confirmation_token), but it does not explain parameter-level semantics such as when cert_path can be empty, how confirmation_token is obtained, or the format of the xml parameter.

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: 'Apply a CAdES-BES (CMS/PKCS#7) attached signature to a FatturaPA XML document.' It also states the output format (.xml.p7m), which distinguishes it from the sibling XAdES signing tool even without naming it.

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?

No guidance is given about when to use this tool versus the sibling it__sign_fattura_xades. The mention of 'Uses the signer microservice when available, falls back to direct signing' describes runtime behavior, not when the agent should select this tool or what conditions make it the wrong choice.

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