get_fins_dividend

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which cover safety and idempotency. The description adds the data returned and the Premium plan limitation, but does not go beyond what annotations imply. 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?

The description is concise with a clear initial sentence summarizing the tool's purpose, followed by a bullet list of returned data and a structured 'Args' section. No extraneous words.

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?

The tool has an output schema, so return values are covered. The description addresses the purpose, data fields, plan restriction, and parameter formats. However, it lacks guidance on required parameter combinations (e.g., can all be null?) and does not mention pagination or limits.

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 coverage is 0%, so the description must compensate. It explains each parameter: code (with format hint), date (single date), date_from/date_to (range). However, it does not detail the purpose of each parameter beyond their names, and the 'anyOf' constraints in the schema are not clarified.

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 clearly states 'Retrieve cash dividend data' and lists specific fields returned (record date, ex-dividend date, etc.). It also specifies the stock code format (5 digits with note about 4-digit codes), distinguishing it from other financial data tools like get_fins_summary or get_equities_earnings_calendar.

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 description mentions '[Supported plans] Premium' indicating a restriction, and provides parameter format guidance (code format, date formats). However, it does not explicitly compare this tool to sibling tools like detect_consecutive_dividend_increase or get_dividend_yield_ranking, nor does it specify when to use this vs alternatives.

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