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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral details beyond these: unpaginated (so cache it), limited to plan coverage, costs 175 credits, and provides the API endpoint. It also explains the purpose of the CIK field. These details meaningfully augment the annotation profile.

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 dense but every sentence earns its place: it states the core purpose, the output fields, caching guidance, a usage tip, constraints, cost, endpoint, and documentation reference. There is no fluff or repetition; it front-loads the purpose and supplies operational details efficiently.

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 zero-parameter list endpoint with no output schema and annotations covering safety, the description is fully sufficient. It explains what is returned (tickers, jurisdiction, CIK, forms array), how to use the result (verify issuer_cik), and constraints (plan coverage, credits, unpaginated). Nothing an agent needs to invoke it 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?

The input schema is empty (0 parameters), so schema coverage is trivially 100%. The description correctly focuses on output semantics, not parameters. With zero parameters, the baseline is 4; the description doesn't need to add parameter details because there are none.

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 (list) and a precise resource: every ticker with insider-trade (Form 4) and/or initial-holdings (Form 3) data, and details the returned fields (jurisdiction, SEC CIK, forms array). This clearly differentiates it from sibling tools like list_companies or list_insider_transactions, which cover broader or different scopes.

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 clear context for when to use it: to enumerate tickers with insider coverage, and specifically to use the returned CIK to verify a filing's issuer_cik. However, it does not explicitly name alternatives or state when not to use it (e.g., vs. list_companies), so it barely misses the bar for explicit exclusions.

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