Insider Trades & Directors Dealings Data

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavior beyond that: the data provenance (unified SEC/BaFin history) and the ordering (oldest to newest). It does not address pagination or result-size limits despite promising 'All' transactions, which is the one notable omission.

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?

Two short sentences, zero filler. Scope and ordering are front-loaded, and the invocation rule ('Pass symbol OR isin') is placed last where it is exactly what the agent needs before calling.

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 two-parameter read-only tool with annotations covering the safety profile and no output schema, the description supplies the key essentials: scope, data sources, and ordering. What it lacks is any hint about volume or pagination for a potentially very large 'all history' result, which is the last thing an agent would want before invoking it.

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% and both parameters are plain undocumented strings, so the description carries the burden and does say something useful: symbol and isin are alternatives ('OR'), which the schema itself does not encode via oneOf. However, it adds no format guidance (ISIN shape, symbol/exchange convention) or consequence of passing both, so it only partially compensates.

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?

States a specific verb+resource+scope: all insider transactions for one company, with the disclosure that SEC and BaFin data are unified. 'One company' implicitly separates it from the market-wide siblings (get_recent_insider_trades, get_insider_toplist, get_featured_insider_trades), but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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 gives a parameter-calling rule ('Pass symbol OR isin') but no when-to-use guidance: it never says to prefer this over get_recent_insider_trades or get_insider_trades_summary, nor when the full unified history is appropriate versus a summary. Usage is only implied by the single-company scope.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that these are curated home-page lists (implying a fixed editorial dataset rather than a raw query), but says nothing about pagination, limit behavior, or result shape.

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?

A single front-loaded sentence with no filler, and the enumeration of list kinds is load-bearing information rather than padding. It could be tightened slightly, but every clause earns its place.

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 should carry more of the return-value and parameter-format burden; it omits what fields each list returns, what the time codes mean, and how limit interacts with the curated lists. Annotations cover safety, so the remaining gap is moderate rather than severe.

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%, and the description meaningfully disambiguates all three 'kind' enum values (buy volume vs officer buy volume vs insider count), which the bare enum cannot convey. However, the cryptic 'time' enum (CM, LM, 7D, 30D) and 'limit' are left completely unexplained, so compensation is only partial.

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 identifies the resource (curated per-company insider-trade lists) and enumerates the three list variants, so an agent can tell what data comes back. It never states a retrieval verb or distinguishes this from the similarly-named sibling get_insider_toplist, leaving some ambiguity.

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 when-to-use guidance, no mention of when a caller should pick this over get_insider_toplist, get_insider_barometer, or get_recent_insider_trades, and no explanation of the required 'time' window. The enum glosses imply usage but do not state it.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds no behavioral context beyond that. It says nothing about how the ratio is computed, the time window semantics, data freshness, or rate limits. The universe mapping it does give belongs to parameter semantics rather than behavior.

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?

A single front-loaded sentence with no filler; the resource name and purpose come first and the market scoping is appended as a parenthetical. It is efficiently sized, though the dense parenthetical packs two distinct ideas into one clause.

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 0% schema description coverage and no output schema, the description is too thin for an agent to call this correctly: the scale/units of the barometer value, how time interacts with the ratio, and what the caller receives are all unstated. It should do substantially more given the structured fields provide almost nothing.

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%, so the description must carry the load. It does explain the 'market' enum meaningfully (US = SEC universe, DE = BaFin universe), which tells the agent the underlying data source, but the 'time' parameter (12M/24M) is left entirely unexplained in both description and 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?

States a specific resource and output (an insider buy/sell ratio gauge) scoped to a market, which distinguishes it from the sibling listing tools like get_recent_insider_trades and get_insider_toplist. It does not explicitly name a sibling it is an alternative to, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as get_insider_trades_summary or get_insider_toplist, which are plausible lookalikes. The only context is the market scoping, leaving selection entirely to inference.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and data-scope profile is covered. The description adds that the output is a ranked company list scoped to a window, but omits result size, ranking metric, and freshness/update cadence.

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?

One sentence, front-loaded with the resource name and its page anchor, with zero filler. Every clause (ranking basis, window scoping) contributes to correct selection.

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 and a single enum parameter, the definition is nearly self-sufficient, but it leaves the return shape (number of companies, ranking metric, tie-handling) unstated. For a ranked-list tool driven by a hidden scoring model, that leaves a meaningful 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?

Schema description coverage is 0%, but the single parameter is a self-describing enum (3M/6M/12M). The phrase 'over the window' confirms it is the evaluation period for insider trading performance, adding modest meaning beyond the raw enum but no format or default detail.

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?

States a specific resource (insider performance toplist) with a clear ranking semantics — companies ordered by how well their insiders traded — which is more than a restatement of the name. It does not, however, name or contrast with any sibling such as get_insider_barometer, so an agent must infer the distinction from context.

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 explicit when-to-use guidance and no reference to alternatives, despite seven closely related insider-trading siblings. The '/insider page' note hints at provenance but does not tell an agent when this ranked aggregation is the right pick over a trade-summary or barometer tool.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the genuinely useful constraint that results are index-restricted and authority-scoped, but says nothing about result shape, ordering, or limits.

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?

Two dense sentences, front-loaded with what the tool returns before the authority/filter coupling. No filler, though the 'authority=bafin' shorthand is slightly telegraphic.

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 and only 3 parameters, the description supplies the aggregation contents and the authority-index relationship. The remaining gap is whether `filter` must accompany a given authority, which is left implicit.

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 only 33% (only `time` is documented), but the description compensates by mapping authority=bafin to DAX/MDAX (Germany) and authority=sec to SP500/DOW (US), which is the key semantic for the otherwise undescribed `authority` and `filter` parameters.

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?

States a specific verb-like resource: per-company aggregates of buy/sell volume, insider counts, and transaction count over a time window. This clearly separates it from sibling trade-listing tools, though it never names a sibling explicitly.

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 scope ('restricted to an index', per-company aggregates) implies when this aggregated view is appropriate, but there is no explicit when-to-use/when-not guidance or routing against get_insider_barometer, get_insider_toplist, or get_company_insider_trades.

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

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful non-annotation context: the return ordering (newest first) and the fields it returns (headline text and a link). It stops short of richer behavioral detail such as result caps beyond the limit bound.

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?

Two tight sentences with the scope and ordering front-loaded ahead of the requirement clause. No filler, though the second sentence largely duplicates the schema constraint rather than earning its place.

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 usefully covers the return shape (headline text and link) and ordering, and annotations cover the safety profile, so an agent has enough to invoke it. The gap is competitive context within a seven-tool insider family, which goes unaddressed.

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 83%, so the schema already documents lang, time, limit, filter, symbols, and transactionType. The description only echoes the limit/time requirement without adding syntax, defaults, or interaction rules between the two, so baseline 3 applies.

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?

States a specific verb and resource (fetch recently published insider transactions), names the data sources (SEC + BaFin) and ordering (newest first), which is genuinely distinguishing. It does not, however, differentiate itself from siblings like get_featured_insider_trades or get_company_insider_trades, so an agent still has to guess which of the family to prefer.

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?

"Requires limit and/or time=24H" is a restatement of the schema's anyOf constraint, not usage guidance. There is no statement of when to choose this tool over get_featured_insider_trades or the other insider siblings, and no exclusions or prerequisites are given.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds only the vague '(charts on the overview page)' pointer, and says nothing about what a 'volume' means (share count vs. currency value), whether results are aggregated per company or per market, or any rate/scope limits.

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?

A single front-loaded sentence with no filler. It is short and readable, though brevity here shades into under-specification rather than genuine economy.

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 2-parameter tool with no output schema and 0% schema description coverage, the description leaves the optional time window unmentioned and the units/aggregation of the returned volumes undefined. An agent cannot predict what it will receive.

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%, and while 'for a market' loosely maps to the required market enum, the time parameter (12M/24M) is completely undocumented in both schema and description. With half the parameters unexplained, the description does not compensate for the coverage gap.

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 names a resource — total insider trade volumes — and scopes it to a market, but supplies no verb and no differentiation from siblings like get_insider_trades_summary or get_insider_barometer, which plausibly return overlapping aggregates. An agent can guess the tool's domain but not confidently distinguish it from its nearest siblings.

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 when-to-use guidance, no when-not-to-use, and no mention of any alternative among the seven sibling insider-trade tools. The parenthetical '(charts on the overview page)' hints at a UI surface but does not translate into a selection rule for an agent.

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

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the bar is lower, yet the description still discloses the result cap ('up to 5 matches') and the exact fields returned. That is useful context beyond the annotations, though it doesn't say what happens on zero or ambiguous matches.

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?

Two tight sentences with the capability front-loaded and the follow-up action second. No filler, every clause carries information.

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 one-param, no-output-schema lookup tool, the description covers what it does, what it returns (fields and the 5-match cap), and how to use the result. Nothing an agent needs to invoke it correctly is missing.

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 100% and the single 'query' param is fully documented there, including the case-insensitive and 12-character constraints. The description restates the same accepted forms without adding format or validation detail, so the baseline 3 applies.

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?

States a specific verb (Find) and resource (companies) plus the three accepted identifier types (name, ticker, ISIN). Also distinguishes itself from the sibling set by naming get_company_insider_trades as the consumer of its output.

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?

Explicitly tells the agent what to do with the result ('Use the symbol or isin with get_company_insider_trades'), which is genuine routing guidance to a sibling. It stops short of when-not-to-use this tool, but for a simple lookup the downstream hand-off is clear.

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