run_volume_profile_reaction_study

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

With no annotations provided, the description carries the full burden, and it discloses several meaningful non-obvious behaviors: the tool compares branches against non-event bars in a matched regime, verifies source/placement/inputs/symbol/timeframe, never ranks or adopts a branch, and explicitly excludes native VP, order flow, and assumed fills. It does not disclose potential side effects such as whether results are persisted to a journal or ledger, which keeps it from a 5.

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 a dense four-sentence block of roughly 90 words; the main verb and resource are front-loaded in the first sentence, but the heavy jargon makes it difficult to parse quickly. Each sentence adds real information, so it is not padded, yet the lack of segmentation or plain-language summary reduces readability for an AI agent.

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?

This is a high-complexity tool: 10 parameters, no output schema, no annotations, and a multi-variant methodology with strict evidence-handling rules. The description covers the methodology, fixed parameters, exclusions, and the combine-prohibition, but omits the return/result format, persistence or side effects, prerequisites, and any meaning for the majority of parameters. An agent would need substantial probing to invoke this tool confidently.

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 10% (the count parameter), so the description needed to compensate but only loosely does. It clarifies that the 60-minute variant supports up to 15,000 rows (relevant to count) and implies expected_symbol/expected_timeframe are verified, but the other nine parameters (folds, signal_from, signal_to, pine_id, study_id, chart_index, event_limit) receive no meaning in either the schema or the description. The methodology terms (70% value area, four branches, 20 bps target) are not mapped to any concrete parameter.

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 a specific verb ('Run') and an unusually precise resource: the frozen descriptive #61b reaction-study variant on CME exchange-volume chart bars with the audited Bushido Volume Profile Context proxy. It further scopes the tool by listing fixed methodology parameters (24 rows, 70% value area, four branches, horizons 1/2/4/8, 20 bps target) and exclusions, which differentiates it from the similar-sounding sibling run_volume_profile_poc_reversion_study. The heavy domain jargon slightly obscures the plain-language purpose, so it doesn't earn a 5.

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 gives no guidance on when to use this tool versus alternatives; no sibling tool is named and no selection conditions are stated. The warning that the 240-minute and 60-minute variants must not be combined is a methodological constraint, not usage routing. This is the weakest dimension for a tool in a large sibling set of research/audit studies.

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