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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about what data is returned (annual history, payment details, total return), but it does not discuss authentication, rate limits, or output format. With rich annotations present, a 3 is appropriate.

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?

The description is a single efficient sentence that front-loads the core purpose and then lists returned data. There is no wasted wording, though it could be slightly more structured by separating purpose from content returned.

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?

There is no output schema, so the description usefully lists the returned content (annual dividend history, payment details, total return). For a simple two-parameter read-only tool, this is nearly complete, though it does not mention possible pagination or response shape.

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 50%: ticker has an example description, but market is just an enum with no explanation. The description says 'one security' but adds no meaning beyond the schema for how market and ticker pair together, what market values mean, or how to discover a ticker. It does not compensate for the coverage gap.

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 states a specific verb (가져옵니다 / fetch) and a specific resource (종목 하나의 상세 배당 정보 / detailed dividend information for a single security), and it enumerates the content (annual dividend history, payment details, total return). It implicitly distinguishes itself from sibling tools by emphasizing detail for one security, though it does not name search_securities or rank_securities.

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?

The phrase '종목 하나의' (one security) implies this is the detail lookup after a security has been identified, which suggests use after search_securities or rank_securities. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no named alternative tool.

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