get_expirations

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

With no annotations, the description carries the full burden. It states it returns a list of dates and implies a read-only operation, but lacks details on date format, sorting, or whether all expirations (including weekly vs monthly) are included. For a simple listing tool, this is acceptable but not exhaustive.

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 well-structured with a summary, usage bullets, args, and returns. The initial sentence is direct and front-loaded. Minor redundancy exists between 'Get available expiration dates' and 'Returns a list of all available options expiration dates', but overall it is appropriately sized and easy to scan.

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?

The description covers purpose, use cases, and return type, but lacks explicit differentiation from sibling tools like 'get_term_structure' and 'get_options_chain' which also deal with expiration dates. It also omits output format details, but given the simplicity of the tool, the description is mostly complete with notable gaps.

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 no description coverage (0%), and the sole parameter 'ticker' is only titled 'Ticker' in the schema. The description adds 'ticker: Stock symbol', providing a semantic clarification beyond the schema. This fully compensates for the missing schema description for the single parameter.

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 it retrieves available expiration dates for a ticker and returns a list of all available options expiration dates. This is specific and distinct from many siblings like 'get_stock_price' or 'get_options_chain', though it does not explicitly name alternatives.

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 a 'Use this tool when' list mentioning specific user queries such as 'When options expire' and 'Weekly vs monthly expirations'. This gives clear context, but does not explicitly exclude related tools like 'get_term_structure' which could also involve expiration dates.

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