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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses a cost (€2.10) and that it is a 'direct' service call, but says nothing about output shape, latency, authorization, or failure behavior for what is likely a paid external lookup.

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: service name, ID, category, price, and required parameter are packed into a few lines with no filler. Structure is functional, though the ID string is of questionable value to an agent.

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 one-parameter, single-output paid service with no output schema and no annotations, the description omits what the document contains and when to request it, leaving an agent unable to judge relevance beyond the Italian label. It is under-specified for the decision it must support.

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%, so the description must compensate, and it only repeats 'Required: taxCode' without explaining the expected format (Italian codice fiscale) or any constraints. It adds essentially nothing beyond what the JSON schema already shows.

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?

It states the tool fetches a DocuEngine service called 'Cariche Attive Persona' with an opaque service ID, but 'Cariche Attive Persona' is an untranslated Italian service name that does not tell an agent what data comes back (company officer/role records for an individual). It is distinguishable from siblings only by the raw name, not by an explained verb+resource.

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 conditions for selecting this over the many similar sibling services (e.g. docuengine_quote_attive_persona, docuengine_esponenti_attivi_azienda), and no exclusions. The only routing help is the price and required input, not usage context.

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