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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond the annotations by disclosing the concrete contents and time windows of the response (7/30/90d insider activity, upcoming Form 144 sales, FY+quarterly financials), which is exactly what matters for an agent when no output schema exists.

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?

A single front-loaded sentence that names the resource first and then itemizes contents; there is no filler. It runs long as an enumerated list, but each item earns its place by describing returned data.

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 one-parameter, read-only tool with no output schema, the description compensates well by enumerating return contents, and the annotations carry the safety profile. The remaining gap is disambiguation from the near-identical sibling 'dossier'.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents that the argument accepts either a ticker or a 10-digit CIK. The description adds no syntax or format detail beyond that, so the baseline 3 is appropriate.

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 resource and scope ('Comprehensive dossier for one SEC-filing company') and enumerates the exact content domains (filings, insider windows, Form 144, financials, 13F holders, peers). It differentiates from non-SEC siblings, but never distinguishes itself from the overlapping sibling 'dossier', leaving a real ambiguity an agent must resolve.

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 never says when to pick this tool over the many adjacent siblings (dossier, fund_holdings, company_insider_pulse, entity_timeline) nor states any prerequisites or exclusions. Usage can only be inferred from the content list, which is guidance by implication at best.

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