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

With no annotations, the description carries the full behavioral disclosure burden and does so well by revealing the $0.001 USDC cost, x402 payment mechanism, no-API-key requirement, and the 402 response when payment is missing. It also discloses that 8-K items are decoded and Form 4 transactions are parsed, which explains processing behavior beyond the schema.

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 three sentences with no wasted wording: the core capability is front-loaded, followed by pricing/payment behavior, then free alternatives. Every sentence adds useful information and the structure is easy to scan.

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 the absence of annotations and output schema, the description is fairly complete: it covers purpose, cost, payment failure, and free alternatives. Still, it omits details an agent might need, such as accepted form identifiers, whether ticker and cik are mutually exclusive, response structure, and error behavior beyond the 402 case.

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 0%, so the description must compensate for bare parameter names. It does explain that the tool accepts 'a ticker or CIK' and hints at relevant form types via '8-K items' and 'Form 4 transactions', but it never explicitly documents the forms parameter, its allowed values, formats, or the relationship between ticker, cik, and forms. This is partial compensation at best.

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 the tool gets recent SEC filings for a ticker or CIK and provides decoded 8-K items and parsed Form 4 transactions. This is a specific verb-resource pairing that makes the main purpose obvious. However, it does not differentiate itself from the sibling check_insider_trades, which likely overlaps on Form 4 data.

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 useful context about the paid per-call model and points to free alternatives ('Free alternative: GET https://longwatch.dev/demo... or POST https://longwatch.dev/try...'). It does not explicitly say when to choose this tool over sibling tools like check_insider_trades or watch_sec_filings, so the guidance is helpful but incomplete.

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