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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: returns a paged feed (newest-first), includes a CourtListener link, and notably reveals a payment mechanism (x402: full feed settles $0.50 USDC; free header preview). Also includes a disclaimer about not being legal advice or solicitation.

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 front-loaded with the key purpose and return structure, then covers parameters, legal disclaimer, and payment info. Every sentence adds value, though the payment note could be separated for clarity. No wasted words, but slightly longer than necessary.

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 no output schema and no annotations, the description covers what the tool returns (list of filings with specific fields), parameters with defaults and examples, and a behavioral note on payment. It lacks error handling or rate limit info but is otherwise comprehensive for its complexity.

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%, so the schema already documents both parameters. The description adds value by providing concrete examples of court ids (deb, nysb, txsb, njb, cacb, flsb) and stating the default for 'days' (14). This helps the agent understand valid inputs beyond the schema's description.

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 clearly states it returns new business reorganization filings with specific details (debtor's counsel, judge, docket number, date, link) and ordering (newest-first). It distinguishes itself from sibling tools like 'preview' or 'diligence_brief' by focusing on a fresh feed of filings.

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 mentions the target audience (restructuring/creditor bar) and a use case (public-docket decision-support), but does not explicitly say when to use or not use this tool versus alternatives like `ch11_preview` or `quick_scan`. Usage is implied rather than guided.

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