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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description adds substantial operational context beyond that: per-row pricing with a call minimum, x402/USDC payment mechanics with no account, 402 sample-row and match-count behavior, sort order, and an explicit exclusion of personal contact data. This is well beyond what the annotations provide.

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 paragraph is dense but front-loads pricing and the usage condition before data-source and row details. Every sentence carries useful information, though the prose is less scannable than a labeled structure would be.

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?

An output schema exists and all 13 parameters are fully documented, so the description only needs to add behavioral and usage context. It covers price, payment flow, data provenance, filter scope, row fields, and privacy limits, which is sufficient for correct invocation. No material gap 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?

Schema description coverage is 100%, so the schema already documents each of the 13 parameters, including examples and the caen-or-judet requirement. The description echoes the filter categories (CAEN, county, city, turnover, employees, net profit, founding year) and sort order but adds no syntax, defaults, or format details beyond the schema. Baseline 3 is appropriate.

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 resource (Romanian companies) and the operation (filtered lead/prospect list) and lists supported filters, so an agent knows this is a list-building tool rather than a single-company lookup. It does not explicitly name or contrast with siblings such as romania_company_search or romania_company_profile, leaving the boundary to inference.

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 clear use cases (sales prospecting, market sizing, supplier sourcing) and a condition ('Use when you need a list of Romanian companies matching criteria'). However, it gives no exclusions or alternatives among the seven sibling tools, so the agent must infer when a different tool is preferable.

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