get_insider_trades

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states that it 'Shows who is buying and selling' without detailing authentication needs, rate limits, pagination, or response format. This leaves significant behavioral gaps.

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 two concise sentences, front-loading the purpose and then adding data volume and filter options. Every sentence is informative with no repetition or fluff.

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?

The description covers core functionality and filter options, and implies output fields (who, amount, price). However, without an output schema, it does not specify exact response structure or pagination, leaving some incompleteness for a tool with 6 parameters.

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%, with each parameter described. The tool description adds context about filter types (e.g., Buy/Sell/Exercise) but does not cover all parameters (e.g., limit is omitted). The added value is minimal 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 clearly states the verb 'Get' and the resource 'insider (director) share transactions for NZX companies', specifying the dataset (4,100+ trades, buy/sell/exercise). It distinguishes from sibling tools by its focus on insider trades, which is not covered by other get_* tools like get_director or get_company.

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 lists filter options (ticker, type, date range, director) that indicate when to use the tool, but it does not explicitly contrast with alternatives or state when not to use it. The purpose is self-contained, so an agent can infer usage context.

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