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

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower. The description adds genuinely useful behavioral context: output includes acceptance timestamps and SEC filing links, results are newest-first, and the scope is 'ALL feeds' – no filtering beyond what params specify. This goes beyond the baseline safety disclosure.

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?

Two sentences, front-loaded with a compelling metaphor ('firehose'), and no filler. Every word contributes to understanding the tool's purpose, scope, and output.

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?

The tool has no output schema, so the description must stand in for return expectations. It does: it names the key fields (acceptance timestamps, SEC links) and ordering. Combined with 100% parameter schema coverage and safety annotations, this is sufficiently complete for an agent to invoke correctly, though pagination semantics are only implied via the cursor parameter.

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 is 3. The description does not add parameter-level semantics beyond the schema; phrases like 'ALL feeds' echo the feeds param default but add no new syntax, formats, or behavioral details.

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 clearly identifies a specific verb, resource, and scope: lists recently ingested filings across ALL feeds (Forms 3/4/5, 8-K, 144, Schedules 13D/13G) with acceptance timestamps and SEC filing links, newest first. It differentiates itself from sibling tools by using 'the firehose' and emphasizing 'ALL feeds'.

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?

Directly states 'Use to see what just came in', giving a clear situational trigger. It doesn't explicitly list alternatives or exclusions, but the implied contrast with more specific sibling tools (e.g., get_insider_trades) is evident from the emphasis on 'ALL feeds'.

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