get_stock_actions

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

No annotations are provided, so the description carries full burden. It merely says 'Get' implying a read operation, but does not explicitly state it is read-only, safe, or require any authentication. No mention of behavior like pagination or side effects.

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 short and to the point, with a clear separation of purpose and args. However, the use of 'Args:' section could be more complete to include all parameters without requiring extra tool configuration. Still, it's efficient.

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?

Despite low complexity, the description is incomplete: no output schema, no explanation of return values, and two undocumented parameters. The sibling tools provide context but the description itself lacks completeness for an agent to use the tool effectively.

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%. The description only covers the 'ticker' parameter with a brief explanation and example. The 'page' and 'export_path' parameters are entirely undocumented, leaving the agent without guidance on their purpose or usage.

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?

Clearly states the tool retrieves stock dividends and splits for a given ticker symbol from Yahoo Finance. The verb 'Get' and specific resource 'stock actions' differentiate it from sibling tools like 'get_financial_statement' or 'get_historical_stock_prices'.

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?

Provides an example ticker 'AAPL' but no guidance on when to use this tool vs alternatives (e.g., get_stock_info for general info, get_historical_stock_prices for price data). No when-not or prerequisite information.

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