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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the description is not burdened with the safety profile. It goes beyond them by disclosing cost ($0.02 per successful call via x402 on eip155:8453) and a rate limit (5 free calls/day across all tools), which materially affects an agent's invocation strategy. It does not cover failure modes or data staleness.

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?

Two sentences: the first front-loads the purpose and returned fields, the second carries the pricing and quota constraint. No filler, and the field enumeration is compact rather than prose.

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 no output schema, the description substitutes by outlining the returned fields and totals, and it discloses cost and quota. An agent can call it correctly without opening the schema, though the absence of any note on ticker/CIK precedence or empty-result behavior leaves a small gap.

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 cik, ticker and limit are already documented in the schema, including the default and max for limit. The description adds no parameter-level guidance (e.g. what happens if both ticker and cik are supplied, or the cost interaction with limit). Baseline 3 is appropriate.

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: 'Recent insider transactions of a US company parsed from SEC Form 4 filings,' and enumerates the payload (who, what, date, shares, price, value, holdings). The Form 4 framing cleanly separates it from sibling tools sec_company and sec_filings.

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 rather than stated: an agent can infer this is the tool for insider activity, but there is no explicit when-to-use or when-not-to-use guidance and no routing to sec_filings or sec_company. No prerequisites (e.g. ticker vs CIK equivalence tradeoff) are discussed.

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