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

No annotations are provided, so the description carries the full behavioral burden. It does useful work by defining jurisdictional scope (US Chapter 11/7, UK Administration/Compulsory Liquidation) and by naming the data returned (court case IDs, appointed liquidators, creditor claim deadlines), but it says nothing about result completeness, coverage outside US/UK, behaviour on no-match, or response size — gaps that matter for a screening tool whose absence of a hit is itself meaningful.

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?

Two sentences, front-loaded with the resource definition followed by usage and exclusion — efficient and easy to scan. The opening sentence is a dense noun list rather than a verb-led statement, which costs a little clarity but not length.

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 one-parameter lookup with no output schema, the description covers what the tool returns (filings, case IDs, liquidators, deadlines) and where it applies, so an agent can judge result adequacy. Minor residual gaps are freshness guarantees beyond the word 'Live' and behaviour when nothing is found.

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 and the schema description coverage is 100%, including accepted identifier forms (legal name, tax ID, registration number) and an example value. With a single fully documented parameter, the baseline is a 4; the description adds no parameter-level detail, but none is needed.

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 ('corporate bankruptcy filings') with the concrete sub-types it covers: Chapter 11/7, liquidation notices, receiverships, and creditor winding-up petitions. It is immediately distinguishable from the closest sibling, verifyCompanyRegistryVat, which it explicitly names as the wrong tool for registration lookups.

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 triggering use case ('screening a business for active or historical bankruptcy filings'), enumerates the jurisdictions and records it covers, and gives an explicit exclusion with the alternative: 'Do not use for general company registration lookups (use verifyCompanyRegistryVat).' That is the full when/when-not/alternative triad.

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