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

Annotations already mark the tool read-only and idempotent, so the description does not need to restate safety. It adds useful behavioral detail about normalized data, pre-computed value_usd, a quote-ready summary string, and the SEC filing link, which goes beyond the structured annotations.

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 carry the essential information with no filler. The primary action is front-loaded, and the additional return-value detail is concise and directly useful.

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 supplies a reasonable summary of return content, including value_usd and the quote-ready string with filing link. It does not enumerate all returned fields or mention default ordering, but the complete parameter schema and read-only annotations cover most invocation needs.

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?

Input schema coverage is 100%, so every parameter is already documented with descriptions and enums. The description adds no parameter-specific meaning beyond mentioning value_usd, but it does not need to compensate because the schema is complete.

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 tool searches normalized insider transactions from SEC Forms 3/4/5, which is a specific verb and resource. It does not explicitly contrast itself with sibling tools like get_planned_sales or cluster_buys, but the resource is specific enough for most agents to distinguish it.

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 provides no guidance on when to prefer this tool over alternatives such as get_planned_sales or trades_before_events. There is no mention of exclusions, complementary tools, or context where this search is the right choice, 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.