search_dividend_events

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the behavioral profile. Description adds use-case context but does not disclose additional behaviors (e.g., rate limits, auth). No contradiction with annotations.

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?

Description is two short, front-loaded sentences. Every sentence is informative: first states the tool's action and scope, second gives use cases. No redundant or extraneous content.

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?

With no output schema, description partially explains output by listing specific fields (announcements, ex-rights, payouts). It does not cover pagination behavior or general output structure, but given the tool's simplicity, this is a minor 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 100%, so baseline is 3. Description adds overall dividend context but does not elaborate on individual parameters beyond what the schema already provides. No parameter-specific enrichment.

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?

Description explicitly states 'Search dividend events' with Chinese translation, and specifies it is pre-filtered to dividends. It lists concrete use cases (announcements, ex-rights dates, payout ratios), clearly distinguishing from sibling search tools like search_events.

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?

Description tells the agent to use it for dividend-related queries, but does not explicitly state when not to use it or name alternatives. The guidance is clear and contextually sufficient, missing only formal exclusions.

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