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

With no annotations, the description still carries useful operational context: it discloses the cost (€4.50, split into €0.10 search + €4.40 document) and that this call yields search results rather than the finalized document. It does not cover auth requirements or what the search result payload looks like.

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?

Front-loaded identification, then cost, required param, and workflow in a compact emoji-delimited block. Dense and scannable, though the emoji markers are somewhat noisy.

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 priced two-step tool with no annotations and no output schema, it adequately covers cost and workflow but omits what the search results contain and how their identifiers feed the patch call. The taxCode format gap also remains.

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?

Only one parameter exists with 0% schema description coverage, so the description must compensate and it does not — 'Required: taxCode' merely restates what the schema already marks required. No format guidance (e.g. Italian fiscal code length/structure) or example is given.

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 resource precisely ('Bilancio XBRL', service ID, 'Camerali' category), but no real verb — the search behavior is only revealed incidentally at the end ('This returns search results'). It does not differentiate the XBRL variant from the many sibling bilancio tools (ottico, riclassificato).

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?

It states the two-step workflow and names the exact follow-up tool (patch_docuengine_bilancio_xbrl), which is genuine routing guidance. However it gives no criteria for choosing XBRL over bilancio_ottico or bilancio_riclassificato, which is the harder selection problem in this sibling set.

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