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

With no annotations, the description carries the burden and does substantial work: it discloses the $0.005 cost, x402 payment mechanism, no-API-key/no-account requirement, 402 failure behavior, and 7-day polling window. It does not reveal success-response shape or cleanup/cancellation semantics, but the payment and persistence behavior are well 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, each earning its place: behavior/duration, cost/payment failure, and free alternatives. Front-loaded with the core monitoring purpose before payment details.

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?

Covers the main operational facts (what is watched, how long, what it costs, paywall behavior) and the schema handles webhook/idempotency_key. But with no output schema and no annotations, the absence of success-response behavior, required identifier semantics, and how a watch is later resolved leaves meaningful gaps for a paid, nested-parameter tool.

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 only 40%, and the description does not compensate for the undocumented cik, ticker, or forms parameters: it never says whether a company identifier is required, whether cik/ticker are alternatives, or what form strings are allowed. It only implies the content types via '8-K events' and 'Form 4 trades,' leaving the agent to guess.

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 action—'Monitor a company between agent runs'—and a concrete resource scope: SEC filings, decoded 8-K events, and parsed Form 4 trades. The 'between agent runs' phrasing and 7-day polling clearly separate it from one-time check siblings like check_sec_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?

Provides clear context: long-running monitoring with 7 days of polling, plus explicit free alternatives (demo link and /try) for when payment isn't wanted. However, it does not explicitly contrast check_sec_filings or state when a one-time check is preferable, so it stops at clear context rather than full when/when-not guidance.

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