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

With no annotations, the description carries the full behavioral burden: it does declare the returned field set and global coverage, which is useful. However, it says nothing about data freshness (real-time vs. delayed), whether future calendars are partial, whether results are capped or paginated, or any auth/rate-limit constraints. A 3 reflects genuine but incomplete disclosure.

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?

Three compact sentences: what it returns, when to use it, when not to. The resource framing is front-loaded and every sentence carries routing or scoping value.

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?

No output schema exists, and the description compensates by enumerating the return fields, which is exactly what an agent needs. The remaining gap is operational detail — freshness/latency and result limits — for a market-data tool where staleness matters.

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?

The single parameter is fully documented in the schema with a pattern, example, and explicit index-code support. The description reinforces the global-stock framing but adds no new syntax or format guidance beyond the schema, so it sits at the high baseline rather than above it.

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 the exact resource (ex-dividend dates, payment dates, yield, payout ratios) and its scope (global stocks), so an agent knows precisely what data this returns. It also distinguishes itself from the two nearest siblings, getSecEarningsEps and getStockEodPrices, by name.

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?

It gives both a positive trigger list (checking ex-dividend dates, record/payment dates, dividend yield, payout ratios, consecutive growth years) and explicit exclusions routing to getSecEarningsEps for EPS reports and getStockEodPrices for daily prices. No inference is required to choose among these three tools.

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