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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds valuable behavioral context beyond them: coverage of 1.55 million filings, 'no API key', return fields, and explicit exclusion of consumer bankruptcies. It does not discuss rate limits or failure behavior, but the safety profile is already covered.

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 sentences, front-loaded with the core action and scope, with no wasted words. The use cases, return fields, coverage, and exclusion are all packed efficiently without redundancy.

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 search tool with no output schema, the description does well by listing return fields, clarifying coverage, and stating exclusions. It does not explicitly disambiguate from the sibling 'bankruptcy_recent' or describe zero-result behavior, but these are minor gaps because parameters are well documented in the schema.

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 baseline of 3 applies. The description does not add substantial meaning beyond the schema; it only reinforces that 'company' accepts a name or part of a name. The schema already documents the date filters, court, and limit adequately.

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 opens with a specific verb and resource ('Find US BUSINESS BANKRUPTCY filings by company name') and immediately distinguishes itself from consumer-bankruptcy searches. It also names concrete output fields, making the tool's scope unmistakable.

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 explicit use cases: 'has this company filed for bankruptcy', corporate distress checks, counterparty risk, and due diligence. It does not explicitly name sibling alternatives or state when not to use it, but the company-centric framing and deliberate consumer exclusion provide clear selection context.

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