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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context about the 'Owned After' split basis, per-security and ownership-form restatement, and the '-' for pre-2023 10b5-1 filings. It doesn't mention pagination or rate limits, but this is a read-only data fetch with thorough column semantics, so a 4 is fair.

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 a single, information-dense paragraph. It front-loads the core purpose and then adds semantic details about the columns and filters. Slightly long but every sentence adds value; for a complex SEC data tool this is acceptable.

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 explains the key columns (Type, 10b5-1, Shares/Price/Value, Owned After) and their meanings, plus date-range and filter support. It doesn't explicitly state the response ordering beyond 'newest first', which is covered. For a 6-param tool with no output schema, this is quite complete, though it could note that maxResults clamping behavior is in the schema already.

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 params are documented in the schema. The description adds meaning beyond the schema by explaining the transactionType semantics (Buy/Sell vs Award/Conversion etc.), and the insiderName matching behavior ('contains every word, case-insensitive'), which is not in the schema. This compensates well.

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 opens with a precise verb+resource statement: 'Get recent insider trading transactions for a stock from SEC Forms 4 and 5, newest first.' It clearly distinguishes from siblings like GetInsiderOwnership, GetInsiderSentimentScores, and GetCongressionalTrades by focusing on Forms 4/5 transactions.

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?

It says 'Use this to understand insider buying/selling activity' and distinguishes Form 3 as 'initial ownership rather than a transaction.' It explicitly cautions that Buy/Sell are only open-market trades, versus compensation/derivative mechanics, and explains the 10b5-1 column meaning, which guides the agent on what this tool is good for.

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