insider_activity

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

With no annotations, the description carries the behavioral burden and does well: it discloses the data source, ordering, field set, exclusions, and that no vendor key is required. It does not mention pagination, error cases, or exact return shape, but nothing in it seems hidden or misleading.

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 dense sentences deliver the core purpose, scope, exclusions, and access requirements without fluff. The most important information is front-loaded and every sentence adds value.

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 simple two-parameter read tool with no output schema, the description covers the essential details: source, fields, ordering, data exclusions, and authorization. It is slightly incomplete around limit semantics and alternative-tool routing, but those are minor given the simplicity.

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 compensate for both parameters. It clarifies that symbol is a single symbol, but it never explains 'limit' or the fact that it controls how many trades are returned. The schema default helps, but the description adds no explicit meaning for limit.

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 specific resource (SEC Form 4 insider trades for one symbol), lists the returned fields, and specifies ordering (newest first). It is clearly distinguishable from sibling tools like ownership or quote because it names the source and the exact data scope.

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 useful selection context by explicitly excluding options and RSU grants and limiting coverage to open-market and direct trades. However, it does not name any sibling alternative or state when to prefer this tool over a related one, so usage guidance is implied rather than explicit.

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