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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered and the description need not restate it. It adds the 'across all companies' scope, which is genuinely useful context, but says nothing about result ordering, the 20-result cap, or whether query matches are fuzzy or exact.

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, zero filler. The content scope is front-loaded and the intended use case follows immediately, so an agent gets purpose and routing signal in the first read.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety and idempotency semantics. For a three-parameter search tool the description is close to sufficient; only the result-ranking and limit-pagination behavior remain unstated.

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?

With schema coverage at 67%, the query and ticker parameters already carry inline descriptions, and the description adds little beyond implying that ticker is an optional narrowing filter rather than a prerequisite. The limit parameter has no schema description and the definition does not clarify its default or truncation behavior, leaving part of the third of undocumented schema unaddressed.

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 opens with a specific verb (search) and enumerates the resource content it indexes: takeaways, outlook statements, management quotes and analyst questions, plus the 'across all companies' scope. That is far more concrete than a bare 'search earnings', though it does not explicitly contrast with the similarly named search_transcripts sibling.

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?

'Best for themes such as tariffs or AI capex' gives a clear positive usage context that helps an agent recognize cross-company thematic queries. It stops short of stating when not to use it (e.g., for verbatim call transcripts or single-company lookups), so the exclusion side is left to inference.

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