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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds real value beyond that by disclosing source restriction (issuer announcements only) and result semantics (empty ≠ no dividend, latest generation retained including cancellations). It says nothing about ordering, pagination or what a truncated result looks like despite a limit param.

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?

Four short sentences, front-loaded with the resource and its provenance before the caveats; every sentence carries information. The weak point is a lack of structural separation between "what you get back" and "how to interpret it", which makes it read as one dense run-on.

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, the description usefully enumerates the returned fields (amount per share, currency, status, dates, source URLs) and sets expectations about coverage gaps. The missing piece is input guidance: an agent still cannot tell what to put in `symbol`, which is the one required parameter.

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 0% and the description never mentions either parameter: nothing on what `symbol` accepts (GPW ticker? ISIN? case sensitivity? the maxLength 80 is unexplained) and nothing on `limit` beyond the schema defaults. The per-share/currency/date detail describes the response, not the inputs, so the two undocumented parameters are left to guesswork.

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 resource (GPW dividend resolutions), its data origin (issuer WZA announcements only) and its payload (amount per share, currency, status, dates, source URLs). The scope language plainly separates it from get_public_price_history and get_public_earnings_calendar without those siblings being named.

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?

"Limited coverage: excludes market data vendor history and predictions" plus "An empty result does not mean the company pays no dividend" gives explicit when-not-to-trust guidance, which is unusually good. It stops short of naming a sibling alternative for the excluded data, so it is not a full when/when-not/alternatives statement.

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