veroq_edgar_insider

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

No annotations are provided, so the description must cover behavioral aspects. It mentions 'COST: 1 credit' and describes the return type, but does not disclose any side effects, rate limits, or data freshness. The description is adequate for a read-only data retrieval operation.

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?

The description is concise with distinct sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence serves a purpose, and the most important information is front-loaded.

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?

The description explains the return type in sufficient detail for a simple list tool. It covers cost and purpose. However, it lacks information on pagination, limits, or error conditions, which could be relevant for heavy usage.

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?

The schema fully covers the single parameter with a clear description and example values. The description adds an example invocation ('{ "ticker": "TSLA" }'), which adds practical value beyond the schema alone.

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 'Form 4 insider trades for a company from SEC EDGAR', which is a specific verb-resource combination. It distinguishes itself from its sibling 'veroeq_insider' by noting it uses a different data source.

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 'WHEN TO USE' section explicitly tells the agent to use this tool for insider buying/selling activity and notes it complements veroeq_insider, providing clear context for when to choose this tool over alternatives.

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