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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the SEC EDGAR registry source and enumerates exactly what the lookup returns, giving useful beyond-annotation context about the tool's behavior and result content.

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, front-loaded sentence contains all essential information: the action, the input, the output fields, and the data source. There is no filler or redundancy, and every phrase contributes to the agent's understanding.

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 lookup with one required parameter and no output schema, the description sufficiently specifies the inputs and the main return fields. It could be slightly stronger by adding edge-case behavior (e.g., unknown ticker) or disambiguating from company_ticker, but overall it is complete for its complexity.

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 input schema already provides 100% coverage with a clear description for the only parameter ('Stock ticker, e.g. AAPL.'). The tool description does not add extra parameter-level detail beyond the schema, so the baseline score of 3 is appropriate.

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') and names a clear resource (stock ticker) with concrete outputs: company name, CIK, exchange, SIC industry code, and headquarters. It also identifies the data source (SEC EDGAR registry), making the tool's scope distinct from siblings like equities_filings or equities_fundamentals.

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 implies the primary use case: when you have a ticker and need company identity metadata from SEC EDGAR. However, it does not explicitly state when to choose this tool over similar siblings such as company_ticker or company_cik, nor does it provide any exclusions or alternative routing guidance.

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