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 company-count limit and the decoding behavior, which are genuine behavioral facts. However, it does not disclose that a subscriber/access token is required (only the 'PRO' prefix hints at it), nor return shape, empty-result behavior, or rate limits for a 25-company batch call.

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 compact sentences with the tier marker and the core action front-loaded, followed by the enumerated flag categories and the batch limit. No filler, though the enumerated category list could arguably be deferred to a return-value section.

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 3-parameter, no-annotation, no-output-schema tool, the description covers what the tool detects and the batch limit, which is the essential part. It does not cover authentication expectations or how many days back 'recent' means, both of which the agent would need to call this correctly.

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 only 33% — only access_token is documented in the schema. The description partially compensates by stating the 25-company cap for the companies array and implying recency for days, but it never defines the days window default or units, leaving the highest-value parameter underspecified.

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 pair (decode, flag) plus the resource (recent 8-K item numbers) and enumerates the exact red-flag categories detected, so the agent knows precisely what it returns. It does not explicitly name the sibling tools filings_by_form or latest_filings to distinguish itself, leaving differentiation implied rather than stated.

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?

Usage is implied: screening a batch of companies for bankruptcy, delisting, auditor change, restatement, or exec departures. The 'up to 25 companies' cap is a useful operational limit, but there is no statement of when to prefer this over latest_filings or filings_by_form, and no exclusions or prerequisites.

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