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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds context by noting it replaces a WhaleWisdom Insider feed subscription, implying a specific data source. No contradictions; additional behavioral details (e.g., data freshness) could be added.

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 concise (3 sentences plus bulleted args), front-loaded with the main purpose, and well-structured. Every sentence adds value without waste.

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 tool with 3 optional parameters and no output schema, the description provides sufficient context: what it returns, how to filter, and its relation to a subscription service. Minor gaps like sorting order or pagination could be included but are not critical.

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 has no descriptions (0% coverage), but the description explains each parameter: ticker as optional filter with example 'NVDA', days_back as lookback window with default 30, min_value_usd as post-filtered minimum value. This adds essential meaning 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 explicitly states it retrieves SEC Form 4 insider trades, specifies the data fields returned (transaction date, insider name & role, shares, price, value), and distinguishes from siblings like get_form_13f_holdings by focusing on insider 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?

The description clearly indicates the tool is for insider trading data, listing optional filters (ticker, days_back, min_value_usd). However, it does not explicitly guide when to use this tool over siblings or mention exclusions.

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