get_price_action_context

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

With no annotations, the description carries full behavioral burden and does it well: it discloses fail-closed verification of source/placement/symbol/timeframe, refusal of Confirm On Bar Close off due to mutable signals, reporting of departures in settings/qualityIssues, and the meaning of 0 on unconfirmed bars. This is substantial transparency beyond the schema.

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?

Three sentences, front-loaded with purpose, then essential caveats; no filler or repetition of schema patterns. Every sentence earns its place.

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?

For a read-only context tool with no output schema and no annotations, the description covers invocation semantics, failure behavior, and a key return-value nuance (0 on unconfirmed bars). Minor omissions are the response shape and the optional chart_index parameter, but these do not prevent correct selection and invocation.

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 40%, but the description adds meaning to all required parameters by mapping pine_id/study_id/expected_symbol/expected_timeframe to 'saved source, study placement, symbol and timeframe' and explaining they are verified fail-closed. It does not explain the optional chart_index, but the required-parameter semantics are significantly enriched.

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 ('Read'), a precise resource ('latest bar's pin-bar, engulfing and sweep readings'), and a strict scope ('only from the exact audited Bushido Price Action Context Pine template'). This clearly differentiates it from get_price_action_context_template and run_price_action_pattern_study by stating it reads existing audited readings rather than returning a template or running a study.

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 states the tool is for reading from the exact audited template and emphasizes fail-closed verification, which tells an agent when this tool is appropriate: when audited price-action readings are needed. It does not name sibling alternatives explicitly, but the 'only from' constraint and refusal of non-conforming studies provide clear contextual guidance.

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