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

With no annotations, the description carries the full burden. It discloses the return format ('clean text') and the unit of extraction ('one item'), which is genuinely useful. However, it says nothing about permissions, whether the URL must be an index vs primary document, rate limits, or failure behavior.

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 the action, resource, and output with zero filler. The parenthetical examples earn their place by clarifying the item-id format.

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 extraction tool with no output schema and no annotations, the description covers purpose, scope, and return format adequately. It stops short of addressing the oddly optional url parameter or error conditions, but nothing critical to a correct call 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 coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema's bare 'item id' by giving concrete item-id examples per form type (1A, 7A, part2item1a, 2-2, 5-2). That syntax guidance helps the agent construct valid calls.

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 gives a specific verb ('Return') and resource ('one item of a 10-K/10-Q/8-K') plus the output format ('clean text'), so an agent immediately understands the operation. It does not explicitly differentiate itself from siblings like financial_statements or full_text_search, but the resource is narrow enough to be distinguishable.

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?

There is no when-to-use or when-not-to-use guidance and no named alternatives among the many siblings. The item-id examples hint at usage but describe formats, not the conditions that select this tool over full_text_search or financial_statements.

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