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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing price (0.25 USDC), the x402 payment rail and supported chains, and failure billing semantics (EDGAR 503 or foreign-filer 404 not charged). These are load-bearing behaviors an agent cannot learn from structured fields.

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 dense sentences: trigger first, return contents second, cost/failure terms last. No filler, and the highest-value routing signal is front-loaded.

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?

Output schema covers return values, and the description still summarizes the verdict-plus-evidence shape. With paid x402 access, the cost and non-billing-on-failure details are the missing pieces an agent would otherwise lack, and both are present.

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%, and the schema itself explains the ticker/name/website matching rules and the optional site parameter in detail. The description adds nothing about 'q' or 'site', so the baseline 3 applies – the schema does all the parameter work.

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?

States a specific verb ('check') and resource ('a US-listed company') and then enumerates exactly what the check covers: going-concern language, delisting 8-Ks, overdue reports, Form 4 direction. An agent can tell this is a synthesized verdict tool rather than a raw-filings tool like get_sec_filings or get_sec_8k.

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?

'Use when an agent needs to check a US-listed company' gives the trigger context, and the 404 note implicitly excludes foreign filers. It stops short of naming sibling alternatives (e.g. get_sec_filings for raw documents, get_insider_trades for Form 4 detail), so routing is by inference rather than explicit.

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