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 usefully discloses the cost (€11.70) and the required input, but says nothing about what is returned, whether the document is generated synchronously or asynchronously, or any auth/rate constraints.

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 with the service identity, price, and required field. The embedded internal ID is arguably noise, but overall there is little waste.

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?

With no output schema, no annotations, and undocumented optional parameters, the description leaves key questions unanswered for a paid document-retrieval service: what the fascicolo contains and how the optional params affect the result.

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 flags taxCode as required. The 'province' and 'companyName' parameters are completely unexplained in both schema and description, so the agent cannot tell whether they are disambiguators, filters, or optional fallbacks.

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 the specific service ('Fascicolo Societa' Di Persone') and labels it as a DocuEngine camerali document, so an agent can infer it retrieves a company file for partnerships. However, it never states the verb or what the fascicolo contains, and it gives no differentiation from close siblings such as docuengine_fascicolo_storico_societa_di_persone or docuengine_fascicolo_societa_di_capitali.

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 when-to-use guidance, no mention of alternatives, and no prerequisites beyond the '📋 Required: taxCode' line. With dozens of docuengine_* siblings, the absence of routing information is a real gap.

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