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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds one genuinely new behavioral trait, case-insensitive matching, which appears nowhere in the schema, but says nothing about result ordering, partial-match behavior beyond 'some part of the name', or how limit truncation is handled.

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 short sentences with no filler, and the core search capability is front-loaded before the case-insensitivity qualifier. Nothing could be removed without losing information.

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 tool with a fully described schema and rich annotations, little is required, but there is no output schema and the description never says what the results contain or how they are ordered. An agent knows how to call it but not what shape of answer to expect.

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 all three parameters (query, market, limit) are already documented with examples and an enum. The description adds only the case-insensitivity note and the KR/US scope that the market enum already encodes, which is marginal value on top of a fully documented schema.

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 names a specific verb and resource (searching dividend securities across Korean and US markets) and enumerates the searchable key types: ticker, English name, and Korean name. It implicitly separates itself from get_security_detail (single-security lookup) and rank_securities (ranking) by framing the operation as a search, but never names those siblings.

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 only implied: the reader infers this is the entry point when they have a partial ticker or name rather than a known security ID. There is no explicit statement of when to prefer get_security_detail or rank_securities, and no prerequisites or exclusions are given.

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