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

No annotations are provided, so the description bears full responsibility. It mentions the tool provides 'key statistics' but does not disclose return shape, time range, pagination, or any access prerequisites, leaving significant behavior unspecified.

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 and directly states the tool's purpose. The first sentence is slightly redundant with the name but overall efficient.

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 single-parameter tool with no output schema, the description gives a basic sense of what it returns (purchases, sales, trends) but lacks details on response format, time periods, or how it differs from similar insider trading tools, leaving some gaps.

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?

The schema has one required parameter, 'symbol', described as 'Stock symbol', which is 100% covered. The description adds no extra meaning beyond confirming it works for stock symbols, so it meets the baseline but doesn't enhance parameter understanding.

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 states it 'provides key statistics on insider transactions, including total purchases, sales, and trends,' clearly identifying a specific resource and purpose. It distinguishes from raw trade lookup siblings like searchInsiderTrades by emphasizing statistics, though it does not explicitly name alternatives.

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 when-to-use guidance or contrasts with sibling tools like getLatestInsiderTrading or searchInsiderTrades. It only implies usage for analyzing insider trading stats but offers no exclusions or decision criteria.

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