insiders_transactions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses nothing beyond the core action—no data source, date range, format, or side effects—leaving the agent to guess what 'insider transactions' entails or what the response looks like.

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 extremely concise—a single sentence with no redundant words. It is appropriately sized for a simple resource but lacks any structural elements like examples or constraints that could enhance usability while still being concise.

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 one simple parameter, the description is minimal but not fully complete. It does not explain what insider transactions are, what data is returned, or how it relates to sibling tools. An agent would need to infer the output format and scope, which is a significant gap.

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 already describes the single parameter 'ticker' as 'Stock ticker', achieving 100% schema description coverage. The description adds no additional meaning or detail about the parameter, so the baseline of 3 is appropriate since the schema does the heavy lifting.

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 states a clear verb ('Get') and resource ('insider transactions'), making the primary action obvious. However, it does not differentiate from sibling tools like insiders_activity, insiders_ownership, or insiders_funds, which could overlap in meaning and leave an agent uncertain which to select.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions, so an agent has no basis to choose this over the many related insider tools.

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