getInsiderTradeStatistics

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds one useful behavioral fact beyond that — the response is summarized statistics (totals and trends) rather than a list of transactions — but says nothing about aggregation window, units, or response shape.

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, but the second largely restates the first ('insider trading activity' vs 'key statistics on insider transactions'), giving the definition noticeable redundancy without extra information. It is front-loaded and readable, just padded.

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 read tool with no output schema, an agent still needs to know the granularity of the statistics (period, per-transaction vs aggregate, per-insider breakdown), and the description only gestures at 'total purchases, sales, and trends'. Adequate to identify the tool, thin on what it actually returns.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the definition. The phrase 'for specific companies or stock symbols' loosely confirms that the symbol scopes the statistics, but adds no format or resolution detail beyond the schema.

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 names a specific resource (insider trade statistics: total purchases, sales, and trends) and the entity it applies to (company or stock symbol), so an agent knows what payload to expect. It does not, however, distinguish itself from close siblings such as getLatestInsiderTrading, searchInsiderTrades, or getInsiderTransactionTypes, so the boundary is left implicit.

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?

There is no when-to-use guidance at all: nothing says this returns aggregates rather than individual filings, and no alternative is named. With three insider-related siblings in the list, the agent has to guess which tool answers a given question.

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