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

With no annotations provided, the description carries the full disclosure burden. It mentions the cost ($0.02 USDC), which is useful, but does not describe data freshness, pagination, rate limits, return format, or any other behavioral traits. For a read operation, it omits safety and limitation details.

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 two sentences with no filler. It conveys the tool's function and pricing efficiently, and every word earns its place. Structure is front-loaded with the primary purpose first.

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?

Without an output schema, the description should clarify what data will be returned. It only states 'insider transactions (Form 4)' without indicating the fields, structure, or any caveats. Given the tool's simplicity, some indication of expected output or limitations is necessary for completeness.

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 each parameter (ticker, from_date, to_date) is already described in the schema. The tool description adds no additional parameter semantics beyond the overall purpose, providing no extra value. Baseline 3 is appropriate given full schema coverage.

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?

The description specifies 'Insider transactions (Form 4) from SEC EDGAR', clearly indicating a verb-like action (get) and a specific resource (insider transactions) with a source. This distinguishes it from sibling tools like get_bars or get_filings, which address different data types.

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 gives no explicit guidance on when to use this tool versus alternatives. It neither mentions alternative tools nor provides contextual cues about when insider transaction data is needed. Usage is only implied by the tool's name and purpose, which is insufficient per the rubric.

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