get_recent_8k_filings

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral detail beyond them: the 5,000-character preview cap, the preview_is_partial flag, and the escalation path via read_more/download_filing_text. Auth requirements and pagination across the limit are not addressed, but the truncation behavior is well disclosed.

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 and the critical preview constraint, then organized into Args/Returns. The Returns block is partially redundant since an output schema exists, which is the only wasted space.

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 two-parameter read tool with annotations and an output schema, the description covers what the agent still needs: the truncation limit, the partial-preview signal, the recovery path, and both arguments. The return-value listing is unnecessary given the output schema, but nothing essential 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 description coverage is 0%, so the description carries the full burden, and its 'Args' section documents both parameters (ticker: stock ticker symbol; limit: number of recent 8-K filings). The explanations are terse but sufficient to invoke the tool correctly.

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 and resource ('Get recent 8-K filings for a company') plus the preview scope, so the agent knows exactly what comes back. It does not, however, distinguish itself from the many filing siblings (get_company_filings, get_filing_content, search_filings), which keeps it below a 5.

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?

Gives a concrete follow-up rule: 'When preview_is_partial is true, follow read_more: download_filing_text(...)', naming the sibling and the triggering condition. It omits when NOT to use this tool versus alternatives like get_company_filings, so it falls short of an explicit when/when-not statement.

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