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

With no annotations, the description carries the full disclosure burden and does well: it states the tool is paid ($0.01 USDC on Base), that no account or API key is required, and that results are as-filed open-market purchases rather than all Form 4 activity. It omits latency, rate limits, and what happens on payment failure, which keeps it below 5.

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?

Telegram-style and front-loaded: cost, then data definition, then payment/auth terms, then endpoint. Every clause carries information, though the trailing raw URL is of marginal use to an agent selecting the tool and the staccato phrasing slightly hurts readability.

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?

For a simple single-parameter read tool the definition covers provenance, price, and auth adequately, but there is no output schema and the description says nothing about the shape of returned rows (fields, ordering, currency/units, timestamps). An agent knows what it is buying but not what it will receive.

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% for the single optional 'limit' parameter (rows 1-100, default 20), so the schema already supplies the range and default. The description adds nothing about paging, ordering, or what a limit actually truncates, so it sits at the baseline for a fully documented schema.

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?

Names a specific verb and resource: insider open-market BUYS sourced from SEC Form 4, filtered to the EP ticker, with the reporting classes (officers, directors, 10% owners) spelled out. It never explains that 'EP' is a ticker or that the buy_insider_* siblings cover other tickers, so an agent must infer the family relationship rather than being told it.

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?

There is no when-to-use or when-not guidance and no routing to alternatives such as the general buy_insider tool or other per-ticker variants. The only selection signal is the embedded ticker and the 'Paid' prefix, which does not tell an agent what to do if it wants a different company or a non-open-market filing type.

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