get_cot_crowding_unwind_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently describes what the tool computes and, importantly, what it does not observe or claim. This gives an agent a clear mental model of the tool's limitations and output nature, though it stops short of describing the exact return format.

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 two sentences with no filler. The main purpose is front-loaded, and the second sentence provides necessary caveats and methodological detail without redundancy.

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 no annotations and no output schema, the description provides useful context about methodology and limitations, but it omits practical invocation details and parameter meanings. It is adequate for an expert who already knows the domain, but less complete for an agent that must decide when to call it versus sibling tools.

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 0%, so the description needs to compensate, but it only indirectly addresses expected_timeframe and expected_symbol by mentioning 'daily FX chart'. It does not explain count or chart_index, leaving two of four parameters underspecified from a semantic standpoint.

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 a specific verb ('Describe') and names a clear resource: an exploratory COT crowded-position unwind proxy on a bound daily FX chart. It adds the proxy's composition (positioning percentiles combined with a 20-day price break), which clarifies the tool's focus. It does not explicitly differentiate from siblings like get_cot_crowding_unwind_overlay_template, but the core purpose is clear.

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 signals when this is appropriate by labeling it 'exploratory' and explicitly stating it never claims to observe orders, stops, institutions, or execution flow, which warns against using it as an actual flow or order tool. However, it does not name alternatives or give explicit when-to-use / when-not-to-use conditions relative to sibling tools such as get_futures_flow_context or get_positioning_context.

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