get_option_expiration_dates

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

With no annotations, the description carries the full burden for behavioral disclosure. The word 'Fetch' clearly signals a read-only operation, which is a critical safety trait. However, it does not disclose any additional behaviors (e.g., data freshness, error handling, rate limits), leaving some depth missing.

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 and front-loads the purpose. The Args section is structured and efficient, with no redundant information. Every sentence earns its place.

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?

For a simple one-parameter fetch tool with an output schema, the description covers the essential aspects: what the tool does and what the parameter means. The return format is not described, but the existence of an output schema makes that unnecessary.

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 has 0% description coverage, but the description compensates with an Args section that explains the 'ticker' parameter fully, including its meaning and an example ('AAPL'). This adds significant value beyond the raw string type in the 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 uses a specific verb 'Fetch' and resource 'options expiration dates' for a given ticker, clearly distinguishing it from sibling tools like get_option_chain (which likely returns full option chains) and get_historical_stock_prices. The purpose is unambiguous.

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 implies usage when option expiration dates are needed, but it provides no explicit alternatives or exclusions. It doesn't mention when to prefer this over get_option_chain or other related tools, so the guidance is only implicit.

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