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

With no annotations, the description carries the burden and does well: it discloses cost ($0.01/call from shop credits), the billing caveat that new top-ups are paused, and that failed/empty calls are free. It also states the data source and a facts-only disclaimer. It doesn't cover rate limits or explicitly confirm auth requirements beyond the credits key, leaving minor gaps.

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 core purpose, followed by return fields, source, disclaimer, and cost. Slightly long, but each clause (billing model, failure semantics, disclaimer) carries real decision value rather than filler.

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, so the description usefully enumerates return fields and totals, and with no annotations it also supplies cost, source, and failure behavior. It is nearly complete for a 3-param read tool; only auth specifics and rate behavior are 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 description coverage is 100%, so the schema already documents ticker, days (1-365, default 90), and limit (1-25, default 25). The description only references 'the window' and 'one US stock ticker', adding no format or constraint detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb+resource: SEC Form 4 insider trading for one US stock ticker. It enumerates the exact data returned (buys/sells/grants/gifts with name, role, date, code, shares, price, shares owned after, filing URL), so an agent knows precisely what it gets. No sibling tool covers insider transactions, so it is clearly distinct.

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 scope is explicit: one US ticker, over a configurable window, sourced from SEC EDGAR. It doesn't name an alternative or state when not to use it, but no sibling overlaps (ticker_brief, token_verdict, x_ticker_pulse are different data). Clear context without explicit exclusions.

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