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

It goes far beyond simple extraction, detailing the response format: a one-line answer with a date, followed by the filer's own sentence, and links to the source filing. This detailed operational context is critical for the agent's expected output quality.

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?

The description is highly efficient, front-loading the answer to the user's core question. It groups the operational details (source, citation, licensing) effectively without introducing extraneous fluff.

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 definition is highly complete for this specialized tool. It provides the data source (SEC EDGAR), the content (specific topics), the expected output format, and the necessary licensing/usage constraints.

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?

Although schema coverage is 100%, the description adds crucial context to the `limit` parameter, explaining that the reply provides a count of total/returned/truncated rows, and that a `more` link is provided for the full board.

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 purpose is stated immediately and extremely specifically, defining the scope to undersea cables, cable landings, offshore wind, and ocean cooling. This narrow and focused topic clearly distinguishes it from the broad list of SEC and company performance siblings.

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?

The description inherently guides usage by listing the exact domain of inquiry—subsea infrastructure and data center energy solutions. While it doesn't explicitly name a tool to avoid, it clearly defines the boundaries of its applicability.

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