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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered elsewhere. The description adds non-obvious context the annotations cannot: the data comes from a quarterly published list with a 'data situației' timestamp, and the service is free — both material for judging staleness and cost.

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?

One front-loaded sentence states the resource, its source, the returned fields, and the freshness marker; 'Gratuit.' is a quick tag on the end. It is dense but every clause carries information an agent needs, 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?

There is no output schema, so the description usefully enumerates what comes back (total, principal, accessories, contested amounts, per-budget breakdown, situation date). Combined with annotations covering the safety profile and a fully documented single parameter, an agent has enough to call it correctly; only the empty-result case is unstated.

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?

With a single parameter and 100% schema description coverage, the schema already explains the CUI format and the RO-prefix tolerance. The description adds nothing beyond what the schema states, so the baseline 3 applies.

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 a specific resource and its source: outstanding company debts to the state budget drawn from ANAF's quarterly published list, with a field enumeration. This is clearly distinguishable in substance from siblings like bilanturi_firma or profil_firma, but no sibling is named to make the boundary explicit.

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?

Usage is only implied: an agent can infer it should call this to check a firm's tax arrears, but there is no statement of when to use it versus bilanturi_firma, verifica_firma, or istoric_firma. The only routing hint (resolve the CUI with cauta_firma) lives in the schema, not the description.

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