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 genuine behavioral facts the schema cannot convey: the service costs €2.30 and belongs to the '[Camerali]' category. However, it says nothing about what is returned, latency, or whether the call is read-only or billed per invocation.

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?

Very short and front-loaded, but the internal service ID and emoji-formatted price/required lines are more metadata dump than useful prose. It is concise without being informative, so size alone doesn't earn a high score.

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 an undocumented parameter, the description should carry the load. It omits what the service returns and how the result is delivered, leaving the agent unable to predict the outcome of the call.

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% for the single taxCode parameter. The description only repeats that taxCode is required, adding no meaning such as format (Italian fiscal code / VAT number), validation rules, or whether it identifies the company or a person. It fails to compensate for the schema 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 is essentially a wrapper label: 'Direct tool for DocuEngine service: Esponenti Attivi Azienda' restates the tool name without explaining in plain language what the service returns (active company officers/directors of a company). With many near-identical siblings (docuengine_soci_attivi_azienda, docuengine_cariche_attive_persona, docuengine_quote_attive_persona), an agent that doesn't read Italian cannot distinguish 'esponenti' from 'soci' or 'cariche'.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives. The only usage-relevant statement is the required parameter, which the schema already enforces. Nothing tells the agent when this service is the right choice over its many siblings.

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