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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: official data source, no API key/login required, output includes form/filing date/direct URL, and a per-call price. This complements rather than contradicts the annotations.

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 tight sentences plus a price tag. Each clause adds value: purpose, source/auth, filtering/output, and cost. No redundancy or fluff.

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?

With 4 parameters and no output schema, the description covers purpose, source, output fields (form, filing date, direct URL), and constraints (lookback, filter). Combined with the schema's per-parameter details, it is sufficient for an agent to invoke and interpret results. Minor omissions like result ordering or empty-result behavior are not critical.

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% with every parameter described, so the baseline is 3. The description mentions 'Filter by form type and lookback window' (mapping to formTypes and sinceDays) but adds no new semantic details beyond what the schema already provides.

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 uses a specific verb ('Watch') with a clear resource ('stock tickers for new SEC filings'), enumerates form types (10-K, 10-Q, 8-K, S-1), and notes the official SEC EDGAR source. It clearly distinguishes itself from sibling tools like live-price-oracle or insider-trading-tracker by focusing on 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?

It provides clear context for when to use: monitoring SEC filings, with free no-login access and filtering by form type and lookback window. It does not explicitly name alternative tools to avoid, but the domain is so sharply defined that usage is unambiguous.

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