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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: the €16.50 price and the required input. However, it omits whether the call is synchronous or needs polling, auth requirements, and what the returned document looks like, which are material for a paid document-generation tool.

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 the cost and required-parameter facts are front-loaded, which is efficient. The internal service ID is noise for an agent but costs little.

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 annotations, no output schema, and zero parameter coverage, the definition leaves critical gaps: what the 'fascicolo storico' contains, how results are delivered, and the meaning of two of three inputs. For a paid document tool with this much surrounding sibling ambiguity, it 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 coverage is 0% and there are three parameters, but the description only flags taxCode as required. The purpose and expected format of the optional province and companyName parameters are never explained, so the description fails to compensate for the documentation gap.

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 largely restates the tool name ('Fascicolo Storico Societa' Di Capitali') and labels it a 'Direct tool for DocuEngine service,' which is a tautology rather than an explanation of what the document actually is. It gives no basis for distinguishing this from close siblings such as docuengine_fascicolo_societa_di_capitali or docuengine_visura_camerale_storica_societa_di_capitale.

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 statement of when to select this tool over the many other DocuEngine fascicolo/visura variants, nor any exclusions or prerequisites beyond the implied 'taxCode required.' An agent is left to infer the routing decision purely from the name.

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