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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the description adds genuine extra context: the paid x402 flow at $0.0056 USDC on Base mainnet, pre-payment rejection of unsupported capabilities, and the false-negative caveat about missing records. It does not discuss error behavior or latency, but the payment and coverage semantics are the high-value disclosures an agent needs.

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?

Three compact sentences, front-loaded with what the tool returns and immediately followed by the coverage constraint. The pricing sentence is dense but factual. No filler, though the payment-mechanics sentence could be trimmed without losing decision-relevant information.

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?

The tool is simple (one parameter, output schema present), so return values need no explanation. Coverage limits, the paid-payment model, and the interpretation caveat are all covered. The missing piece is disambiguation from the near-identically named sibling tool, which matters given the crowded entity/company toolset.

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 coverage is 100% and the entity_id field is thoroughly documented ('Stable CelerAPI entity ID returned by search_company. Pass it unchanged.'). The description adds only the indirect hint that the entity must already be 'resolved'. With the schema carrying the parameter burden, 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 states a specific verb and resource: 'retrieve normalized authoritative insolvency information for a resolved legal entity where supported by its registry.' It scopes coverage to GB Companies House, so an agent knows what data it is getting. The one gap is that it never distinguishes itself from the sibling 'get_company_insolvency', leaving the entity-vs-company split implicit.

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 gives clear usage context: the entity must be resolved, coverage is currently GB Companies House only, and unsupported capabilities are rejected before payment. It also warns that absence of a record is not proof of financial health, which prevents misreading an empty result. It stops short of naming an alternative tool for non-GB entities or for the company-level variant.

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