get_gamma_by_expiration

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

No annotations are provided, so the description carries the full burden. It discloses the resource and bucket types but does not mention authentication requirements, data latency, or error behavior. The read-only nature is implicit from 'Get' but not explicitly stated.

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?

One sentence, front-loaded with the action, and includes an enumerated list of buckets without any filler words. Every element 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?

The tool is simple (one parameter) and has an output schema, so the description need not detail return values. The bucket list is sufficient for basic understanding, though it would benefit from a note on how it differs from get_gamma_curve.

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 description mentions 'for a ticker', which references the single parameter, but adds little beyond the schema's 'Ticker' title. It does not explain format or constraints, yet the parameter is self-explanatory given the low complexity.

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 action ('Get'), the specific resource ('strike-aligned gamma decomposition'), and the precise expiration buckets (combined, nearest, first_weekly, first_monthly, all_other_expiries). This distinguishes it from sibling tools like get_gamma_curve and get_gex_by_strike.

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?

No explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The intended use is only implied by the verb 'Get' and the resource name.

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