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

Annotations already declare the safety profile (readOnly=false, idempotent=false, destructive=false, openWorld=false). The description adds one genuinely useful behavioral trait, distinguishing body-text evidence from listing-only hits, but does not explain why a 'search' is flagged non-read-only or clarify the listing-only-hit concept. With annotations carrying the safety load, this is adequate but thin.

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 sentences, reasonably front-loaded on the core action, with no padding. However, the identical bilingual restatement doubles length without adding information for a single-language reader, and the second clause describes output behavior instead of operational guidance.

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 no explanation. But for a six-parameter search with 17% schema coverage and no usage routing, the description omits parameter semantics (filters, limit, language) and any when-to-use context, leaving meaningful gaps.

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 only 17% (just the 'query' field). The description names the global/China split and call/notes content, partially covering 'region', but leaves limit, date_from, date_to, and output_language entirely undocumented in both schema and description. It fails to compensate for the low coverage.

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 (search) plus resource (earnings-call transcripts and meeting notes) and scope (global and China), and describes the output nuance of body-text vs listing-only hits. It does not explicitly name siblings like search_filings or search_research, but the meeting-transcript resource is distinct enough to tell it apart.

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/when-not guidance and no reference to alternatives such as get_evidence or search_filings. The agent must infer from the resource type alone that this is the right tool for meeting-note lookups, with nothing ruling out the siblings.

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