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

With no annotations provided, the description carries the full disclosure burden and does well: it lists the concrete outputs (CIK, official name, tickers, exchanges, SIC, fiscal year end), making the tool's behavior predictable. It doesn't address failure modes or ambiguous matches, but for a simple lookup this is a solid 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 with no filler: the first states the core action and outputs, the second gives workflow guidance. The most important scoping information is front-loaded, and every word earns its place.

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 single-parameter lookup tool with no output schema, the description is nearly complete: it covers input types, output fields, and usage ordering. It could briefly mention that CIK is also accepted as input (as the schema does), but this is a minor gap given the schema is available.

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?

The schema already documents the single parameter fully (ticker, company name, or CIK) with an example, so schema coverage is 100%. The description adds the context of resolving to SEC identity but doesn't add parameter-level detail beyond the schema.

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 uses a specific verb ('resolve') with a precise resource ('stock ticker or company name' → 'SEC identity') and enumerates the exact output fields. This clearly distinguishes it from sibling tools like filing_search or financials, which focus on retrieving filings or data rather than identity resolution.

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 instruction 'Start here before other Filings Intel calls' is an explicit usage directive that tells the agent to use this tool first in a workflow. It does not name specific sibling alternatives or spell out when not to use each, so it falls just short of a 5.

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