spread_vertical

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

Since no annotations are provided, the description carries the full burden for behavioral disclosure. It only says 'Analyze' implying a read-only operation, but lacks details on return format, potential side effects, rate limits, or any special requirements. The parameter list touches on argument semantics but does not cover behavior.

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-loaded with the purpose, followed by a structured argument list. It is appropriately sized for the tool, with no redundant fluff, though the argument list could be formatted with a table or bullet points for readability.

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 has 5 parameters and no output schema, so the description should explain what analysis results are returned, how to interpret them, and when to use it relative to other spread tools. None of that is present, making the description barely minimally viable for an agent to invoke correctly.

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?

Schema coverage is 0%, so the description's parameter list is essential. It provides brief but clear meanings for all 5 parameters, including format for expiry and enum for option_type. This adds value beyond the bare schema, though it could enrich strike price descriptions with ordering relationships.

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 states 'Analyze vertical spread' which clearly identifies the operation and resource. It distinguishes from sibling tools by specifying the spread type (vertical vs diagonal, straddle, etc.), though it could be more explicit about the analysis output.

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 guidance on when to use this tool versus alternatives. With over 30 sibling tools including other spread strategies, the description provides no decision context or exclusions, leaving the agent to infer applicability.

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