ib_find_short_roll

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

With no annotations, the description carries the full burden. It discloses auto-detection logic and the prerequisite of TWS/IB Gateway, but it does not explicitly state whether the tool places orders or only performs analysis. The word 'find' implies read-only, but this is not clarified, nor is the output behavior described.

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 sentence, a bulleted list of modes, a prerequisite statement, and a concise parameter list. It is appropriately sized, front-loaded with purpose, and every sentence adds value.

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?

Given the tool's complexity and lack of output schema, the description does not explain what the 'candidates' output looks like or provide examples of results. It covers purpose and parameters well but leaves out return format and potential error conditions, making it incomplete for a tool of this sophistication.

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?

Despite 0% schema description coverage, the description includes an Args section that explains every parameter (symbol, port, account, strike, expiry, right) with examples, defaults, and auto-detection behavior. This fully compensates for the schema's lack of descriptive text.

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 opens with a specific verb and resource: 'Find roll, spread, or covered call/put candidates using real-time IB data.' It clearly distinguishes itself from sibling tools by explaining the auto-detection mode based on existing positions (short option, long option, long stock), which is a unique feature.

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 clear usage context by specifying the three position-based modes and the requirement for TWS or IB Gateway running locally. However, it does not explicitly mention alternatives or when not to use this tool, so it lacks explicit exclusion guidance.

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