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

No annotations are provided, so the description carries the full burden. It does disclose a cost (€2.30) and the required field, which is genuinely useful behavioral context for a paid document service. It does not state whether the call is synchronous or asynchronous, how the document is returned (inline vs. downloadable via get_docuengine_documents), or whether results are cached.

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, which is good, but the identifier hash is noise for the agent and the required-field note restates the schema. The price line is the only distinct piece of information carried.

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-generation tool with no annotations, no output schema, and 0% parameter coverage, the description omits critical context: what the returned document contains, whether it is synchronous, and how to retrieve the result. It is not sufficient for an agent to invoke this correctly without additional assumptions.

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 coverage is 0% for the single parameter. The description repeats the schema's required field name ('taxCode') but adds no semantics: whose tax code (company vs. person), expected format (11-digit partita IVA vs. 16-char codice fiscale), or whether an error is returned for an invalid value. With only one parameter the burden is small, but the repetition adds nothing.

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 identifies the operation via its Italian name 'Soci Attivi Azienda' (active shareholders of a company) and gives a service ID, but neither the description nor the title translates or explains what the document actually reports. An agent unfamiliar with Italian chamber-of-commerce terminology cannot distinguish this from docuengine_esponenti_attivi_azienda or docuengine_quote_attive_persona without external knowledge.

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?

'Direct tool for DocuEngine service' implies this is the call to use for this specific document, and the required taxCode signals a lookup keyed to a company. There is no explicit when-to-use vs when-not-to-use statement, no mention of the sibling esponenti_attivi (which sounds like the same thing), and no note about async status checking despite check_async_status/get_docuengine_request_status siblings.

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