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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description nevertheless adds real behavioral context beyond them: the return format (markdown by default, raw HTML when get_markdown=False), a citation convention (first line is the beatandraise.com viewer link), and the accepted URL shapes. It does not say what happens with very large documents (truncation, size limits), which is the one missing behavioral trait.

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?

Purpose and the sibling exclusion are front-loaded in the first two paragraphs, with format and identification guidance following. The Args block restates parameter names, but given 0% schema coverage that restatement earns its place. Minor slack in phrasing such as 'a fraction of the document, with a link highlighting it'.

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 read-only fetch tool with an output schema, the description covers what an agent needs: how to identify the document, the two output formats, and the citation convention. The remaining gap is operational behavior on large filings (pagination, truncation, response size), which matters for whole 10-K retrieval and is neither in the description nor the annotations.

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 coverage is 0%, so the description must carry the whole burden, and it largely does: every parameter is named with meaning, an example value (cik "0000320193", filename "ef20060722_8k.htm"), a default (get_markdown True) and the fallback behavior for cik ('found from the accession number when left out'). It also documents the two mutually exclusive identification modes (accession_number+filename vs url). The one gap is that it never states as a hard requirement that one of those two modes must be supplied, leaving all-optional params ambiguous.

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 opens with a specific verb+resource ('Fetch a filing document's content from storage') and immediately distinguishes itself from the closest sibling, get_filing_item, by explaining that the sibling returns a single Item with a highlighting link. An agent can tell which tool to call without inspecting either schema.

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?

It states exactly when to use the sibling ('For one section of a 10-K, 10-Q, 8-K or 20-F ... use get_filing_item instead') and when to use this tool ('to read the actual text of a whole 10-K, 8-K, exhibit, or any other filing document'). The alternative and the selection condition are both explicit, including the negative scoping note that the url is 'not a company website'.

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