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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is fully transparent. The description adds the 'live' nature and the focus on 'most recent' filings, which is helpful, but it does not disclose response shape, pagination, or rate-limit behavior. This is acceptable given the strong annotation coverage but not exceptional.

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 a single, information-dense sentence that front-loads the core behavior and then adds the key filtering capability. No wasted words.

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 simple read-only tool with four parameters and no nested output schema, the description plus annotations cover the essential invocation context. The main gap is the absence of any hint about the response format, but the tool's simplicity and strong annotations make this a minor omission.

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 75%, and the description adds relationships that the schema does not: 'for a ticker or CIK' clarifies the mutual-exclusivity between cik and ticker, and 'filter by form type' maps directly to the forms parameter. This goes beyond simply restating the schema fields.

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 states a specific action and resource: it returns live SEC EDGAR submissions (10-K, 10-Q, 8-K, ...) for a ticker or CIK, with optional form-type filtering. This makes its purpose unmistakable and distinguishes it from sibling tools like equities_fundamentals and equities_ticker.

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 clearly implies when to use this tool: when you need recent SEC filing data for a company identified by ticker or CIK, and optionally filtered by form type. It does not explicitly name alternative tools or exclusion criteria, but the use case is specific enough for an agent to route correctly.

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