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

Annotations already mark the operation as read-only and non-destructive, and the description adds valuable context beyond that: the data source (SEC EDGAR), cryptographic attestation, verification URL, and per-call cost. It does not disclose edge cases such as missing filings or delisted tickers, but the annotation coverage lowers the burden.

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 core purpose is front-loaded in the first clause, with source, verification, and pricing following in a compact sequence. The attestation and verify URL are somewhat promotional but not excessively bloated; the description remains efficient.

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 single-parameter read-only tool, it covers the source, the nature of the output, verification, and pricing. However, there is no output schema, and the description omits return shape, error behavior, or ticker format details, leaving some ambiguity for an agent invoking the tool.

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?

With schema description coverage at 0%, the description was expected to compensate, but it never explains what to pass or the expected ticker format. The parameter name 'ticker' is self-evident, yet the description adds no additional meaning beyond what the schema already exposes.

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 states a specific function: reading SEC EDGAR Schedule 13D/13G beneficial ownership filings and identifying activist versus passive 5%+ shareholders. It clearly distinguishes itself from the large set of sibling get_* tools by naming its regulatory source and specific output signal.

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?

No explicit when-to-use guidance is given, and it never contrasts with sibling tools like get_sec_insider_trading or other SEC-related data tools. Usage is implied by the tool name and general description, but there are no stated exclusions or alternative selection criteria.

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