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

Annotations cover read-only/idempotent/open-world safety, but the description adds substantial value beyond them: it discloses the exclusion of forms 3/4/5/144/13D/13G, the inclusion of the 10 most recent filings, the full field set, and crucially the paid x402 USDC payment flow with the PaymentRequired behavior on unpaid calls. That payment detail is essential and not in annotations.

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 dense sentence is front-loaded with the use case, then the return payload, exclusions, and payment terms. It is information-rich and well ordered, though the long parenthetical field list is heavy and could be trimmed.

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?

Given no output schema, the description compensates by enumerating returned fields and the filings links, and it explains the payment model. It is nearly complete for a no-required-param profile lookup, with only minor gaps such as error behavior for unknown tickers.

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% and provides the cik/ticker examples, so the schema is largely self-sufficient. The description adds the semantic rule that the tool resolves either a ticker or CIK interchangeably ('resolves a ticker or CIK'), which clarifies the either/or relationship beyond the schema text.

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+resource ('resolves a ticker or CIK and returns the EDGAR profile') and enumerates the returned fields, distinguishing it from siblings filings, financials, and search. The title and description make the scope unambiguous.

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 opening 'Use when you need the official facts about a US-listed or SEC-registered company' gives clear usage context, and the exclusion of insider/beneficial-owner forms is explicit. However, it does not directly name siblings (e.g., 'use financials for X') to route the agent among alternatives.

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