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

Annotations already cover the read-only/idempotent/non-destructive profile, but the description adds real value beyond them: the data provenance (SEC EDGAR, unaffiliated), a per-call cost model ($0.03 per successful call, failed calls free), and the edge case that an option/RSU vest produces two rows in one filing. These are exactly the behavioral facts an agent needs.

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?

Front-loaded with the core purpose, then efficient supporting sentences on the vesting edge case, data source, and pricing. Dense but each sentence carries distinct, useful information; only minor trimming would help.

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 an output schema and rich annotations already present, the description still fills the remaining gaps: provenance, cost model, and the two-row vesting behavior. Nothing an agent needs to invoke or interpret the call correctly is missing.

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%, so ticker_or_cik, limit, and api_key are fully documented in the schema itself. The description adds no parameter syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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+resource (recent insider buying and selling at a US public company), names the identifying key (ticker or CIK), and enumerates the exact fields returned. This clearly distinguishes it from the generic sibling company_filings.

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 makes the use case (insider Form 4 activity) clear, but never names an alternative or states when NOT to use it. It does not route the agent to company_filings for broader filing needs, leaving comparison to inference.

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