dividend_history_deep

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

Discloses data source (yfinance), output structure (up to 60 entries, annual totals, trailing yield), and examples. No annotations provided, so description carries full burden; could mention rate limits or error handling but sufficient.

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?

Well-structured with sections (overview, benefits, output list, args, examples). Every sentence adds value, no fluff.

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?

Describes all key outputs (full history, annual totals, trailing yield, total dividends) and includes examples. Output schema exists but description is still thorough.

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?

Only parameter 'symbol' is explained with examples (NSE or global stocks like RELIANCE, TCS, AAPL). Schema has 0% description coverage, but description fully compensates.

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?

Description clearly states it provides 10-year dividend history with yield calculation and annual summary, listing specific outputs. It distinguishes from sibling 'dividend_history' by being 'deep' and mentioning data sources.

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?

Explicitly contrasts with paid alternatives (Bloomberg/FactSet) and mentions free source (yfinance). Provides usage examples and context for when to use this tool (deep history vs basic).

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