insiders

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

With no annotations, the description carries the full burden and does add real behavior: one row per transaction, the fields returned (shares, price, value), currency semantics, and a 12-month history cap on the free tier. It omits permissions/auth requirements, pagination or result-size limits, and what happens when both filters are omitted, so it stops short of full disclosure.

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?

Three sentences, front-loaded with purpose, then output shape, then the tier constraint — no filler. It is slightly dense but every sentence contributes, and the most decision-relevant facts come first.

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?

With no output schema, the description commendably describes the returned row shape, and it flags the free-tier history cap. However, for a four-parameter, no-required-parameter tool it leaves the date filters and the both-filters-omitted case unexplained, so an agent cannot fully predict the query behavior.

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 description coverage is 0% across four parameters, so the description must compensate. It loosely covers ticker and owner, but 'start' and 'end' are never mentioned, and no format (date string shape) or filtering semantics are given for the date range that the 12-month note implies exists.

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?

Names the resource (insider transaction filings) and enumerates the subtypes it covers (buys, sells, option exercises) plus the query keys (ticker and/or owner name). This is unambiguous against siblings like company_profile or fundamentals, though it never explicitly routes the agent away from any other tool, which is what a 5 requires.

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?

'For a company ticker and/or an owner name' implies the conditions under which the tool is the right pick, and the free-tier note tells the agent a limitation exists. There is no explicit when-to-use/when-not guidance and no named alternative, so usage is only implied.

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