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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully conveys that the data is 'live' and quantifies the dataset size and geographic scope, but it does not describe return shape, pagination behavior, or authentication expectations beyond what the schema already states.

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 description is a single front-loaded sentence that includes substantive scope, scale, and jurisdiction examples, with no wasted words. It earns every word and remains immediately skimmable.

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?

Given 8 optional parameters, no output schema, and no annotations, the description is only moderately complete. It establishes the resource and dataset scope well but omits default result behavior, filter-combination behavior, and expected response contents, leaving some end-to-end calling context to the agent.

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 all 8 parameters. The description adds only a high-level 'search and filter' framing and does not explain advanced semantics like how filters combine or how absence of filters behaves, keeping this at baseline 3.

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 states a specific verb and resource: 'Search and filter 132,000+ live European insolvency, liquidation, and bankruptcy filings' across 32 jurisdictions. It also clearly differentiates from the sibling search_distressed_auctions by targeting insolvency filings rather than auctions.

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 description gives no explicit guidance on when to use this tool versus search_distressed_auctions, get_company_details, or get_coverage_stats. Usage context is only implied by the focus on insolvency filings, and no exclusions or alternative-routing conditions are mentioned.

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