ibkr_contract_search

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

No annotations provided, so the description must carry the full burden. It mentions 'fuzzy matching' which hints at behavior, but does not disclose outcomes on failure, read-only nature, or any rate limits. No contradictions with annotations (none exist).

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?

Single, efficient sentence of 13 words. No unnecessary text, front-loaded with key action and resource.

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 existence of an output schema and simple single-parameter tool, the description is mostly complete. However, it could hint that output contains contract identifiers needed by sibling tools, which would aid agent reasoning.

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 description coverage is 100% with a single parameter 'pattern' already described with examples. The description adds little beyond restating that search is by name or symbol; baseline 3 is appropriate.

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?

Description clearly states 'Search for contracts by name or symbol using IB's fuzzy matching', specifying verb (search), resource (contracts), and method (fuzzy matching). This distinguishes it from sibling tools like ibkr_quote or ibkr_option_chain.

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 implied usage is to find contract IDs, but no explicit guidance on when to use this vs alternatives like ibkr_quote or ibkr_option_chain is provided. No exclusions or prerequisites mentioned.

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