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

With no annotations, the description carries the full behavioral burden, yet it only discloses a price (€2.10) and a category tag. It does not say whether this is a read-only lookup, what authentication it needs, whether the cost is billed per call, or what the response contains.

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?

It is short and front-loads the service and resource name, which is good. However, the emoji-decorated price and required lines are formatted as marketing metadata rather than informative prose, adding noise without adding understanding.

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 paid, parameterized DocuEngine lookup with no annotations and no output schema, the description is far too thin: it omits what the document contains, its legal/regional scope, and any return expectations. It does not do enough to help an agent choose it over the dozens of sibling document tools.

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, so the schema provides only a bare string type. The description's "Required: taxCode" merely repeats the required array already present in the schema and adds no format guidance (e.g., Italian fiscal code structure), leaving the parameter undocumented.

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 ("Quote Attive Persona") and labels it a "Direct tool for DocuEngine service," which adds no meaning about what the operation actually does. It never states a verb or explains the resource beyond the Italian phrase in the name, so an agent cannot tell from the text whether this returns a person's shareholdings or something else.

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 exclusions, and no reference to alternatives. The sibling docuengine_cariche_attive_persona and the many visura/quote-family tools are indistinguishable from this one based on the description, so the agent has no routing signal.

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