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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the tool 'finds' and 'accesses' information, implying a read operation, but does not disclose return format, pagination, response structure, or any limitations. This is a significant gap for a tool with no output schema.

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?

The description is two sentences and front-loaded with the primary action. However, the second sentence largely restates the first ('essential company details' vs 'company information', 'stock ticker symbols' vs 'stock symbol'), making it slightly redundant. It remains appropriately compact.

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 one-parameter search tool, the description gives a clear purpose but omits return value details, which matters because there is no output schema. It does not specify whether the result is a single company object, a list of filings, or the exact fields returned. This is a moderate gap, making it minimally viable.

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% for the single parameter 'symbol' (described as 'Stock symbol'). The description adds only synonyms ('stock ticker symbols') and no further semantic detail, so it does not improve on what the schema already provides. Baseline 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 clearly states the tool finds company information and regulatory filings using a stock symbol. This specific verb+resource combination distinguishes it from sibling tools like searchCompaniesByCIK and searchCompaniesByName, which use different identifiers.

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 clearly implies usage for when a stock symbol/ticker is available ('using a stock symbol', 'based on stock ticker symbols'). It does not explicitly mention alternatives or exclusions, but the context is clear enough to guide selection among the many search-related siblings.

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