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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the price (€13.70) and the required taxCode, but omits whether this is a paid order with side effects, whether delivery is synchronous or asynchronous (many siblings like check_async_status and get_docuengine_request_status suggest async workflows), and what the result looks like.

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 short and front-loaded, leading with the service identity and keeping the price and required-parameter notices scannable. It is efficient, though the emoji-delimited lines carry mostly metadata rather than explanatory content.

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 paid document service with four parameters, no parameter documentation, no annotations, and no output schema, the description is too thin. It should at least clarify the operation type, whether results arrive synchronously or via a status-check flow, and what the shippingAddress/shipmentRecipient fields imply about physical delivery.

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% across 4 parameters, and the description only restates that taxCode is required — information already present in the schema's required list. The optional phone, shippingAddress, and shipmentRecipient parameters (which suggest physical delivery) are entirely unexplained in both schema and description.

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 names a specific resource (Certificato Artigiano, [Camerali]) and identifies it as a DocuEngine service, which helps distinguish it from the many sibling document tools. However, it never states the actual action — whether it orders, retrieves, downloads, or generates the certificate — so the verb is effectively 'direct tool for service X', which is closer to an identifier than a clear purpose.

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?

There is no guidance on when to use this tool versus alternatives such as docuengine_certificato_di_iscrizione, docuengine_certificato_storico, or the generic document-download siblings. The only context is the service name itself, so the agent must infer applicability from the resource label alone.

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