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

With readOnlyHint already declaring safety, the description adds substantial context: the SAMPLING TRAP (newest N filings, not the whole window) with an explicit warning against totaling rows, hard caps on since_days/limit, which fields are derived, the SEC Form 4 source, and that caveats ride tool_notes.

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?

Dense but front-loaded: purpose first, then return shape, then caps, then the trap, then provenance and siblings. Nearly every sentence earns its place, though the since_days/limit default-and-cap restatements duplicate the schema and cost some conciseness.

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, yet the description spells out the return keys {summary, since_days, count, buys} and per-row fields, covers the sampling caveat, provenance, and where notes live. An agent has everything needed to call and interpret it 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 coverage is 100%, so the schema already documents all four parameters including the min_value null-drop and common_only filtering rules. The description largely restates defaults and caps already present in the schema, adding little beyond it, so 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+resource with scope: open-market insider PURCHASES (SEC code 'P') across the ~5.3k-ticker Oxford Ledge catalog, framed as a daily insider screen. It names the siblings it pairs with (ol_insider_cluster_scan, get_insider_activity), so an agent can place it without opening a schema.

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?

Gives clear context ('a daily insider screen') and points to related tools it pairs with, plus a critical warning not to treat results as a period total. However it stops short of explicit when-to-use-vs-alternative routing (it never says when to prefer this over ol_insider_cluster_scan or get_insider_activity).

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