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

No annotations are provided, so the description carries the full burden. It does disclose the return shape (matching tickers with names and sectors), which helps, but says nothing about case sensitivity, prefix vs substring matching behavior, how 'tracked' scoping works, or pagination.

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 tight sentences with the search scope front-loaded and the return content second. Nothing is wasted, though the second sentence is somewhat redundant with what a response schema would ideally convey.

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 two-parameter read tool this is nearly adequate: it covers purpose and return content. The gaps — undocumented limit semantics, no safety annotations, and no differentiation from screen_companies — leave meaningful room for an agent to guess wrong.

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%: the query parameter is documented in the schema, but limit is not described anywhere. The description's 'ticker or name' echoes the schema description rather than adding syntax or matching-rule detail, so it does not compensate for the coverage gap.

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+resource ('Search tracked companies') and the searchable fields (ticker or name), which is clear enough for selection. It does not distinguish itself from the sibling screen_companies, which is plausibly also a company-discovery tool, so it falls short of a 5.

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?

Usage is implied by 'search by ticker or name' — an agent can infer this is a lookup for a known company. However, there is no explicit when/when-not guidance and no routing to screen_companies for criteria-based discovery, which is the main ambiguity given the sibling list.

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