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 without the description. The description adds ordering behavior ('newest filing first') and the identifier precondition, but says nothing about pagination flow, result shape, or the relationship between limit and the opaque cursor.

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 sentences, zero filler, with the resource and scope front-loaded before the identifier constraint. Nothing needs trimming and nothing important is buried.

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 nine-parameter, no-required-parameter read tool with full schema coverage and no output schema, the description covers the essentials: what is searched, the scope, the ordering, and the identifier precondition. It is slightly thin on how pagination is expected to be driven across calls, but that gap is minor given the schema's cursor documentation.

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%, so all nine parameters are already documented, including the ticker/cik alternative and the cursor semantics. The description's only added parameter fact ('Either ticker or cik is required') is already present verbatim in both schema fields, so it contributes no new semantics.

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 ('Searches individual insider trades'), names the filing sources (SEC Form 4 and 5), and gives the scope (one company) plus the sort order (newest filing first). It does not name or contrast itself with the closest siblings (insider_get_transaction, insider_list_recent, insider_list_cluster_buys), so it stops short of full sibling differentiation.

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 supplies a hard precondition ('Either ticker or cik is required'), which is genuinely useful invocation guidance. However, it gives no when-to-use/when-not guidance relative to the other insider tools, so an agent must infer that this is the general list endpoint and insider_list_recent/cluster_buys are the specialized variants.

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