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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the data provenance (SEC filings) and a non-advice disclaimer, which is modest value beyond the annotations, but says nothing about match quality, fuzzy/partial-name behavior, or what happens when no company is found.

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?

Three short sentences, front-loaded with the core capability, with no redundant restatement of the title. The provenance and disclaimer sentences are brief and earn their space, though 'Free' is slightly promotional.

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 should clarify what a search returns, e.g. a ranked list of candidate matches versus a single resolved company, and how ambiguous queries behave. That return-shape information is missing, which matters for a search tool that can plausibly return multiple companies.

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 description coverage is 100%, with the schema itself explaining that q accepts a name or ticker and giving an AAPL/apple example, plus the limit range of 1 to 25. The description adds no parameter-level detail beyond that, 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?

The description states a clear bidirectional verb-and-resource operation: map a company name to a ticker or vice versa, sourced from SEC filings. It does not, however, distinguish itself from the sibling get_company, which an agent would reasonably see as overlapping.

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 rather than get_company, nor any prerequisites or exclusions. The word 'Free' hints at a complementary lookup service but gives no routing rule, leaving the search-vs-get decision entirely to inference.

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