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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds that results come from recent insider filings and include official names and CIK numbers, which is useful. It says nothing about matching semantics (fuzzy/prefix vs exact), ranking, or how many results are returned when multiple companies match.

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, zero padding, and the core purpose is front-loaded before the usage conditions. Every clause carries information an agent needs.

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 only two parameters and an existing output schema, the description need not describe return values, and it correctly focuses on data source and trigger conditions. The one gap is the undocumented 'limit' parameter, which neither the schema nor the description explains.

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%: 'query' is documented in the schema with an example, but 'limit' has no description anywhere. The description's phrase 'ticker fragment' echoes the schema rather than adding format guidance, and it does not explain what 'limit' controls. Baseline 3 is appropriate given the schema carries the query 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?

The description gives a specific verb and resource ('Look up tickers and official company names') and names the data source (recent insider filings, SEC CIK). It is clearly distinct from data-fetch siblings like get_company_context or get_financials, which retrieve content rather than resolve an identifier, though it does not explicitly name those 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?

It states two concrete trigger conditions: the user names a company without a ticker, or a ticker lookup returns nothing. That is real when-to-use guidance. It stops short of naming the alternative resolution path (e.g. get_company_context) or any exclusions, so it is strong but not complete.

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