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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds value beyond that: it discloses the cost ($0.002/call), the public-domain source, and the shape of the returned content (summary, impact direction, link). It stops short of describing pagination or per-call rate behavior, keeping it at a strong 4.

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?

Front-loaded with the resource and scope, then triggers, then the cost, then the sibling disambiguation. Every sentence carries information. The '$0.002/call' clause sits mid-description and momentarily interrupts the flow, a minor structural blemish.

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?

No output schema exists, but the description explains what comes back (summary, impact direction, link), and covers the forms, window and issuer dimensions. For a filtered, read-only lookup tool this is nearly complete, with only limit/pagination behavior left unstated.

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 75% (forms, since, ticker documented; limit is not). The description still adds meaning by spelling out the form categories (8-K items, Form 4, 13D/G, S-1/424B, bankruptcy) and the notion of a time window, reinforcing how 'forms' and 'since' behave. It adds context over the schema rather than merely restating it.

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 resource (SEC EDGAR filings) with explicit scope ('touch ONE US issuer in the window') and enumerates the covered form types (8-K by item, Form 4, 13D/G, S-1/424B, bankruptcy). It also names the sibling it is not (news_for), so an agent can distinguish it without opening either schema.

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?

Gives concrete when-to-use triggers ('before earnings', 'when a stock moves without news') and states the routing rule explicitly ('Use for SEC filings of one issuer; for headlines use news_for'). Both the use case and the alternative are named, leaving nothing to inference.

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