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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that output is raw, unparsed item text and discloses a per-request price, which is useful context; it says nothing about payload size or rate limits.

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 states purpose immediately, followed only by a clearly delimited pricing block. Nothing in the prose is wasted, though the pricing boilerplate occupies more space than the functional description.

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 values need not be described. However, for a tool whose enum mixes 10-K and 8-K item codes and whose required fields shift by filing_type, the description omits the conditional-argument model entirely, leaving a real gap for an agent assembling a call.

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 100%, so the baseline of 3 applies. The description contributes no additional parameter meaning — it does not explain that the enum spans two different item numbering schemes (10-K Items 1–16 vs 8-K Items 1.01+) or which fields are conditionally required.

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 raw text Items from an SEC filing'), and the word 'raw text' signals it returns unparsed content rather than metadata. It does not explicitly contrast itself with the sibling get_financial_filings, leaving the item-level vs filing-level distinction to be inferred.

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 guidance on when to use this over get_financial_filings or the other filing-related siblings, and no mention that item/quarter/accession_number must be matched to the filing_type. An agent gets no routing or prerequisite information from the description.

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