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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-data nature is covered. The description adds only the data scope ('tracked by InsiderAlpha') and says nothing about result ordering, pagination, rate limits, or how partial matches behave.

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 no filler, but it is arguably under-specified for a tool with a pagination parameter rather than merely concise.

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 read-only search with annotations covering the safety profile and no output schema, the description covers purpose adequately. It leaves the 'limit' parameter unexplained and gives no sense of result shape or breadth of matching, which is the main remaining gap.

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 50%: 'query' is documented in the schema as 'Company name or ticker fragment', which the description merely restates, while 'limit' (default 20, max 50) is undocumented in both places. The description does not compensate for that gap or explain matching 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 ('Search companies') plus the data domain ('tracked by InsiderAlpha') and the match keys ('by name or ticker'). It is clearly distinguishable from siblings like search_filings and search_insiders, though it never names an alternative explicitly.

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 when-to-use guidance, no prerequisites, and no exclusions or alternatives. The only hint is the implicit framing of a name/ticker lookup, which an agent could infer from the name alone.

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