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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the two-step search-then-finalize flow, the nature of the return (search results), and the cost model (€4.50 total, €0.10 search / €4.40 document). It does not mention auth requirements or rate limits, but the pricing and workflow disclosure is above average.

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 definition is compact and front-loaded: service identity first, then price, required input, and workflow, each on its own labeled line. Every line conveys distinct information with no filler.

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 single-param, no-annotation, no-output-schema tool, the description covers the workflow and cost but leaves the output content and auth requirements unstated, and does not disambiguate the sibling bilancio variants. Adequate but with visible gaps.

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?

There is one parameter at 0% schema description coverage, so the description must supply its meaning. It only restates '📋 Required: taxCode' without explaining that this is an Italian fiscal code/VAT identifier or its expected format, adding essentially no semantics beyond the schema's required list.

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 names the specific DocuEngine service (Bilancio Ottico) with its ID and domain tag '[Camerali]', and clarifies that it is a search step rather than the finalizing step. It distinguishes itself from its patch_ sibling, though it never explains what a 'Bilancio Ottico' is relative to the bilancio_riclassificato and bilancio_xbrl siblings.

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?

The two-step workflow is stated explicitly: this tool returns search results and 'patch_docuengine_bilancio_ottico' selects and finalizes. That gives a clear when-to-use and which-alternative signal. It stops short of explaining when to choose this bilancio variant over the riclassificato/xbrl variants.

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