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

With no annotations, the description must carry the full behavioral burden. It discloses the price (€0.90) and required parameters, but omits read-only vs. write behavior, authentication needs, return format, and side effects, leaving significant behavioral gaps.

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-loads the service name and key facts (price, required params). It is mostly efficient, though it redundantly repeats 'Visura Protesti Azienda' and includes an internal ID that may not help the agent act.

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?

Given no annotations, no output schema, and 0% parameter description coverage, the description is incomplete for a paid service tool. It identifies the service and price but lacks parameter definitions, usage guidance, and any indication of what the tool returns or how to interpret results.

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 by explaining the parameters. It only repeats the parameter names and their required status, adding no meaning about what reaCode and cciaa represent, their format, or how to obtain them.

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 a specific DocuEngine service ('Visura Protesti Azienda') and includes an ID, so the agent knows it retrieves that particular report. However, it does not explain what a 'Visura Protesti Azienda' contains or distinguish it from close siblings like docuengine_visura_protesti_e_pregiudizievoli_azienda, leaving the exact scope ambiguous.

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 explicit when-to-use or when-not-to-use guidance is provided. The service name implies it should be used to obtain this specific report, but there is no mention of alternatives or prerequisites, so an agent must infer selection criteria.

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