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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety bar is low. The description still adds genuine context beyond them: the source is public filings, results include derived analytics (return vs S&P 500, ticker/company validation), and it carries an explicit 'not investment advice' caveat. Pagination and default period behavior remain unstated.

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?

A single front-loaded sentence that begins with the scope and payoff ('in one call'), followed by short filter and disclaimer sentences. It is dense but every clause carries information; the field enumeration is slightly redundant given an output schema exists.

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 an output schema present and full parameter description coverage, the description's job is scope, source, and caveats — all covered (public filings, no investment advice, available filters). Nothing an agent needs in order to issue a correct call is missing.

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%, so the baseline is 3. The description adds meaning only for two of five parameters — ticker filtering and buys/sells — and implicitly gestures at matchedOnly via 'a check that the filed company matches the ticker,' but leaves `days` and `limit` entirely to the terse schema text ('1 to 1095', '1 to 1000').

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?

Opens with a specific verb-and-resource pairing — stock trades from President Trump's public financial disclosures — and enumerates the exact payload fields, so an agent can distinguish it from list_congress_trades, list_insider_trades, or get_whale_trades without opening any 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?

The description states the supported filters (ticker, buys/sells) and the data source, which implies when to reach for it, but never names a sibling alternative or a when-not-to-use condition — with nearly 40 siblings in this family, an explicit contrast to congress/insider trade tools would have earned a 5.

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