get_latest_10k

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, so the bar is lower, yet the description still adds substantial behavior: the preview is capped at 10,000 chars covering only the cover page and first statements, and a preview_is_partial flag signals truncation. That is exactly the operational context an agent needs to sequence follow-up calls.

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-loads the purpose and preview scope, then uses Args/Returns sections for the rest; the paging instructions earn their place. Slight redundancy in restating the return dictionary fields that the output schema already covers keeps it from a 5.

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?

An output schema exists so return keys needn't be explained, yet the description goes further and documents the truncation/windowing workflow. Nothing an agent needs to call this correctly or chain into follow-up tools 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?

Only one parameter and schema coverage is 0%, so the description must carry the burden; it does describe ticker as 'Stock ticker symbol'. That is minimal but sufficient for a single self-evident input, though it adds no format or validation detail.

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 the latest 10-K filing for a company') and immediately scopes the return ('filing link plus a SHORT preview of its text'). It distinguishes itself from download_filing_text by positioning that sibling as the follow-up for the full text, so an agent can tell the tools apart without opening schemas.

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 an explicit conditional route: 'When preview_is_partial is true, follow read_more' and names the exact alternative calls (download_filing_text with offset or search). The when/when-not split between this tool and the full-text downloader is unambiguous.

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