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

With no annotations, the description carries the full burden and does well on cost, payment rail, and zero-auth, plus the sourcing rule ('as filed'). It omits behavioral traits an agent needs: whether the call blocks until payment settles, what happens on failed payment, pagination/freshness of the data, and the response shape.

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?

Very short and front-loaded, with price and access conditions stated early. The telegraphic style ('Paid.', bare URL) reads as machine-oriented and leaves a little interpretation work, but nothing is padded.

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 paid, unauthenticated data fetch with no output schema, the definition covers source, scope, price and endpoint, which is enough to decide to call. It stops short of describing the returned records or payment/failure behavior, which matters given the monetary cost.

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% for the single 'limit' parameter (rows 1-100, default 20), so the schema already does the work. The description adds no meaning about ordering, count semantics, or how limit interacts with the paid call.

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 and resource: insider BUYS for ticker FUNC from SEC Form 4, narrowed to open-market purchases by officers, directors and 10% owners. It clearly separates this from sell/option-grant data and from other buy_* families, though it never explicitly says it is the per-ticker instantiation of buy_insider.

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?

Usage is implied by the data source description rather than stated as guidance. The cost and access conditions ('$0.01 USDC on Base. No account, no API key') act as prerequisites, but there is no when-to-use vs alternative guidance and no exclusions such as 'this excludes sales or derivative filings'.

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