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

Annotations already declare readOnlyHint and openWorldHint, so safety and scope are covered. The description adds that results are identity records (CIK + ticker), which is genuinely useful given there is no output schema, but it says nothing about result multiplicity, ordering, or the empty/near-miss case for an open-world search.

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 with the resource, the matching key, and the return value; nothing is repeated and nothing is wasted.

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 does minimally cover return values (CIK and ticker). However, for an open-world search over a huge registry, it omits pagination/result-count behavior and result ordering, and never explains the one undocumented parameter.

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 50%: 'q' is documented in the schema, but 'limit' (integer, default 10, max 50) is undocumented in both schema and description. The description's 'by name or ticker' reinforces the fragment semantics of q but does not compensate for the missing limit semantics.

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 and resource ('Find public companies') plus the identifying inputs and what it resolves to (CIK and ticker), so an agent knows this is a lookup/resolution tool. It does not differentiate itself from the many sec_* siblings (sec_company_profile, sec_company_filings, sec_filing_search), leaving the agent to guess which entry point to use for a company lookup.

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?

There is no statement of when to use this versus sec_company_profile or sec_filing_search, no prerequisite or exclusion note, and no hint that this is the first step before fetching filings. The agent must infer usage from the sibling names alone.

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