get_dividend_yield

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the tool gets data but does not clarify if the yield is daily/monthly, how missing data is handled, or any other behavioral traits beyond the basic operation.

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 concise with two lines of text plus an argument list. It is front-loaded with the main action and then details parameters. No unnecessary words.

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?

Given that an output schema exists (not shown), the description need not explain return values. However, for a tool with three parameters and no annotations, the description could benefit from mentioning data frequency or default date behavior. It covers the essentials but has room for improvement.

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%, so the description compensates by explaining each parameter: ticker is a stock/ETF symbol with examples, and date parameters are specified to be in YYYY-MM-DD format. This adds valuable semantic meaning beyond the bare schema.

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 clearly states the tool retrieves historical dividend yield data for stocks or ETFs, using the verb 'get' and specifying the resource type. It distinguishes itself from sibling tools like 'get_dividends' which likely returns actual dividend payments, not yield.

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?

The description provides parameter formats but does not offer any guidance on when to use this tool versus alternatives such as 'get_dividends' or 'get_fundamentals'. No context on prerequisites, limitations, or typical use cases is given.

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