get_vix_term_structure

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

Annotations already indicate safe, read-only, idempotent behavior. The description adds value by specifying that the tool returns a regime classification (contango, backwardation, flat), which informs the agent about the output format beyond the schema, enhancing transparency.

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 three sentences, starting with the core function and then adding interpretive context. Every sentence is informative and free of redundancy.

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?

Despite lacking an output schema, the description covers the key return values (regime, spot, VIX3M, VIX6M) and provides enough context for the agent to use and interpret results. The annotations further assure safe usage, making the tool adequately specified.

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?

No parameters are defined in the input schema, so the baseline is 4. The description does not need to add parameter semantics, and it correctly omits unnecessary detail.

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 the VIX term structure from real CBOE data, specifying components like spot VIX, VIX3M, and VIX6M. This distinguishes it from other 'get' tools in the sibling list, which focus on different data sources or metrics.

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 context on the meaning of contango/backwardation and their market implications, but does not explicitly state when to use this tool versus alternatives. There is no guidance on prerequisites or conditions for use, leaving usage somewhat implied.

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