searchInsiderTradesByReportingName

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing behavioral beyond the annotations: no indication of match semantics (exact vs partial name), pagination, result caps, or whether historical depth is limited.

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, front-loaded with the purpose. The 'using the Search Insider Trades by Reporting Name API' phrase is filler that restates the tool name and could be dropped without loss.

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-parameter read-only lookup with full schema coverage and no output schema, the definition is minimally sufficient, but it leaves the key practical question — whether the name is an exact match or a partial/fuzzy search — unanswered.

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% for the single required parameter, so the baseline is 3. The description reinforces that the parameter is a reporting person's name but does not clarify matching behavior or accepted formats beyond what the schema already states.

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 pairs a specific verb ('Search') with a specific resource ('insider trading activity') and a specific access path ('by reporting name'), which lets an agent distinguish it from symbol-based insider siblings. The second sentence and the 'using the ... API' clause are largely restatements rather than added precision.

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?

'Track trading activities of specific individuals or groups involved in corporate insider transactions' implies the use case, but there is no explicit statement of when to prefer this over searchInsiderTrades, getLatestInsiderTrading, or getInsiderTradeStatistics. The agent must infer the alternative from naming alone.

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