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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint, so the safety profile is covered. The description adds the returned content and a terse 'Pro.' tier signal, but says nothing about pagination behavior or how the limit interacts with the default of 20.

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?

One tight sentence, front-loaded with the resource and scope. The trailing 'Pro.' is an unexplained fragment that costs some clarity but doesn't bloat the text.

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 return fields (execution date and split ratio), and annotations carry the safety profile. A simple two-parameter read tool needs little more; only the ambiguous 'Pro.' and absent usage routing hold it back.

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 100%, with both ticker and limit fully documented including the default of 20 and the 1-500 range. The description adds nothing beyond naming 'ticker', so the baseline of 3 applies.

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 (stock split history) scoped to a ticker, and even names the returned fields (execution date, split ratio). It's clear enough to distinguish from siblings like dividends or financials, though it never explicitly contrasts with them.

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?

No indication of when to use this versus related siblings (e.g., dividends, stock_candles) or of any prerequisites. The only hint is the cryptic trailing 'Pro.', which implies a tier requirement but is not explained.

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