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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the useful behavioral fact that resolution is bidirectional, but it does not say how a bare string is disambiguated between ticker and CIK, nor what happens on an unknown symbol (error vs empty result).

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 short sentences with zero filler; the conversion semantics come first and the downstream-use hint second. Nothing is repeated from the name or title unnecessarily.

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?

With no output schema, the description correctly names the return values (CIK, ticker, company name) and the reason to call it. It is complete for a one-parameter lookup, with only the not-found/ambiguity behavior left implicit.

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 the single parameter already documents both accepted forms with examples. The description restates the either/or input nature but adds no format, casing, or normalization guidance beyond the schema, so baseline 3 applies.

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 (convert/resolve) and resource (ticker ↔ SEC CIK + company name), including both directions of the mapping. An agent can immediately tell this is a lookup/identifier-resolution tool and distinguish it from the filing, concept, and snapshot 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?

Explicitly says to use it to obtain the CIK needed by search_filings, which chains it to a concrete downstream tool. It stops short of stating when NOT to use it (e.g., that it returns no filing or price data, which is what the other siblings cover).

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