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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful operational context beyond that: pricing ($0.01 USDC per successful call via x402 on Solana) and an equivalent HTTPS endpoint, which matters for agents choosing an access path.

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?

The description is dense but front-loads the core purpose, then adds pricing and an alternate endpoint in separate sentences. It is appropriately sized for a data-retrieval tool, though the first sentence is long and could be split for 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?

With no output schema, the description compensates by enumerating the returned data: reporting owner and role, transaction codes and meanings, shares, price, value, acquired/disposed, holdings after, derivative details, and buy/sell totals. That plus pricing and endpoint information makes it complete enough to call correctly.

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%, including the type enum and limit bounds, so the schema already carries parameter semantics. The description does not add syntax or behavioral details beyond what the schema provides, so the baseline 3 applies.

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: retrieving the latest SEC Form 4 insider-trading filings for a ticker or CIK, parsed from EDGAR ownershipDocument XML. The detail about reporting owners, transactions, and buy/sell totals clearly separates it from siblings like sec_13f, sec_edgar_search, and sec_financials.

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 establishes the input context (ticker or CIK) and implies use for insider-trading research, but gives no explicit guidance on when to choose this over sec_edgar_search or sec_13f. Usage is inferable but not clearly routed.

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