get_stock_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the data categories returned; it does not mention error handling for invalid tickers, rate limits, data freshness, or any other behavioral traits. This is a significant gap for a tool with no annotation support.

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 reasonably concise with a lead sentence and a bullet-like list of information categories. The list is long but informative, and the Args section is clearly separated. It earns its length, though 'Other' is a slightly vague inclusion.

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?

An output schema exists (though not shown), so return structure is presumably covered. The description adequately explains the input and general content, but lacks usage context and behavior beyond listing categories. For a simple one-parameter tool, it is minimally viable but not rich enough for full autonomy.

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 schema coverage is 0%, so the description must compensate. The Args section explicitly defines 'ticker' as 'The ticker symbol of the stock to get information for, e.g., "AAPL"', adding clear meaning and a concrete example beyond the bare string type.

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 'Get stock information for a given ticker symbol from yahoo finance,' which specifies a verb, resource, and input. The long list of categories (e.g., 'Stock Price & Trading Info', 'Financial Metrics', 'Dividends') distinguishes it from specialized sibling tools like get_historical_stock_prices or get_yahoo_finance_news.

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?

There is no explicit guidance on when to use this tool versus its siblings. The description lists what data is returned but does not say 'for a comprehensive overview use this' or 'for historical data use get_historical_stock_prices.' No exclusions or alternatives are mentioned.

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