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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'Get', implying a read-only operation, but does not disclose what specific insider trading data is included (e.g., transaction types, dates, holder names), any pagination behavior, or response structure. This is minimal disclosure for a tool with no other context.

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 sentence with no wasted words. It is front-loaded with the main action and resource, making it easy to parse quickly.

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 simple one-parameter read-only tool with 100% schema coverage, the description is minimally sufficient. However, it lacks any context about what 'insider trading data' includes, and the absence of annotations or output schema means the agent has no additional signals to understand the return format or scope. It is adequate but not complete.

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 provides 100% coverage for the single required parameter 'symbol' with a clear description. The tool description adds 'company' and 'insider trading' context, which maps well to the symbol parameter. Since the schema does the heavy lifting, the description adds a modest amount of meaning beyond it.

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 uses a clear verb+resource structure: 'Get company insider trading data.' It tells the agent this tool retrieves insider trading information for a specific company. However, it does not distinguish this from sibling tools like getInsiderTradeStatistics, getLatestInsiderTrading, or searchInsiderTrades, which also target insider trading.

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 guidance on when to use this tool versus the many insider-trading-related siblings. It does not specify whether this is for historical transactions, recent filings, or statistics, nor does it mention alternatives or exclusions.

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