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

With no annotations, the description carries the full burden. It states the tool returns a comprehensive list of transaction types and gives examples, implying a read-only operation. However, it doesn't disclose response structure, pagination, or any limitations. For a simple zero-parameter catalog, this is adequate but not rich.

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 at two sentences, but the first sentence includes the redundant phrase 'with the All Insider Transaction Types API,' which repeats the tool's name. The second sentence adds value with examples of transaction actions. It could be tightened to a single, more efficient sentence.

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 list tool with no parameters, no output schema, and no annotations, the description provides enough context to understand what the tool returns: a list of insider transaction types with examples. It doesn't discuss related use-cases or prerequisites, but given the tool's simplicity, the description is reasonably 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 tool has zero parameters, and the schema is empty (100% coverage). Baseline for 0 parameters is 4. The description doesn't need to add parameter details and doesn't explicitly mention the lack of parameters, but the schema makes it obvious. No additional parameter semantics are needed.

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 clearly identifies the tool as providing a list of insider transaction types, with examples like purchases, sales, and corporate actions. It distinguishes itself from data-retrieval tools like getInsiderTradeStatistics or searchInsiderTrades by focusing on the taxonomy of transaction types, but it could be more explicit that this is a reference/static list rather than trade data.

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 alternatives. It doesn't mention that this list of transaction types could be used to filter or interpret insider trading data from other tools (e.g., searchInsiderTrades), nor does it provide any exclusion criteria. The description is purely capability-focused, not usage-focused.

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