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

With no annotations, the description carries the full burden. It usefully discloses the price (€13.70), which is real behavioral context not present in the schema, but omits whether this is a paid purchase, whether delivery is asynchronous and requires check_async_status, and how the document is returned. For a paid document-retrieval service that is a significant gap.

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 text is short and front-loaded with the price and required parameter, which is good. But it repeats the service name twice and the internal ID plus 'Direct tool for DocuEngine service' are filler that consume space without informing tool selection.

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?

No output schema and no annotations mean the description must be self-sufficient, yet it provides no return-value or lifecycle information and leaves 3 of 4 parameters undocumented. For a paid, likely shipped document service this is inadequate.

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% and the description only identifies taxCode as required, matching the schema without adding meaning. The three optional parameters (phone, shippingAddress, shipmentRecipient) are left entirely unexplained in both places, even though they imply the certificate is physically shipped — an important behavior the agent cannot infer.

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 essentially restates the tool name ('Certificato Di Iscrizione') and wraps it in boilerplate ('Direct tool for DocuEngine service'). It does not explain what a certificate of registration contains or why an agent would request it. It also fails to distinguish it from close siblings like docuengine_certificato_artigiano, docuengine_certificato_storico, or the various visura_camerale_* tools.

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?

Aside from naming the one required parameter (taxCode), there is no guidance on when to select this tool over the dozens of sibling DocuEngine products. No prerequisites, no exclusions, no routing hints are given.

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