preflight_bookmap_flow_price_join

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 that the tool creates no candidate, outcome study, chart change, or order, and it qualifies Bookmap flow as a single-venue futures proxy rather than spot-FX-wide flow. It stops short of describing failure modes or file modification behavior, but the main safety-relevant traits are covered.

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 three focused sentences, each earning its place: purpose, data caveat, and safety guarantee. It is dense but not bloated, and the key constraints are front-loaded.

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 description explains purpose, data semantics, and non-mutation, but with no output schema it should also indicate what a successful verification returns or how mismatches are surfaced. Given the domain-specific jargon and six parameters, the description is not fully self-sufficient.

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 only 17%, and the description only implicitly covers expected_symbol/expected_timeframe via 'EURUSD M1 or M5' and session_file via 'local Bookmap Collector session'. It does not clarify count, interval_seconds, or minimum_intervals, which are important to this verification workflow.

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 uses specific verbs 'Read' and 'verify' against a precise resource: a local Bookmap Collector session joined to the active EURUSD M1/M5 chart. It also explicitly states it creates no candidate, outcome study, chart change, or order, which sharply differentiates it from the many research and study sibling tools.

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?

It is clear this is a preflight verification step to run before relying on Bookmap flow as a proxy for EURUSD chart context. It does not explicitly name alternative tools or spell out when-not-to-use conditions, but the read-only preflight framing and data qualification give sufficient guidance for selection.

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