veroq_insider

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

Describes cost (2 credits) and output format (transaction list with fields, summary stats). No annotations provided, so description carries burden well, though no mention of authentication or rate limits.

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?

Well-structured with sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence adds value; no fluff. Front-loaded with key purpose.

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?

Complete for a single-parameter read tool: covers purpose, usage guidance, cost, and output structure. No missing critical information.

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 coverage is 100% for the only parameter 'ticker'. Description adds an example JSON ('{"ticker": "AAPL"}'), adding clarity beyond schema.

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?

Clearly states the verb 'get', resource 'insider trading activity', and specific source 'SEC Form 4 filings'. Distinguishes from siblings like 'veroq_edgar_insider' by focusing on executive/director activity.

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?

Provides explicit 'WHEN TO USE' section: to check insider buying/selling. Lacks explicit alternatives or when-not-to-use, but context is clear enough.

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