get_cot_crowding_unwind_overlay_template

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

With no annotations, the description carries the full behavioral burden. It explicitly discloses that the overlay does not fetch or infer CFTC data, orders, stops, or execution flow, and that COT values are supplied externally. This is meaningful transparency beyond basic purpose.

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?

Two tightly written sentences with no filler. The main action and resource are front-loaded, followed by a precise behavioral clarification. Every phrase adds value.

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 zero-parameter, no-output-schema template tool, this description is nearly complete: it names the artifact, its inputs, and what it excludes. The only minor gap is not explicitly stating the return format, but the name and description strongly imply a Pine Script overlay.

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?

The input schema has zero parameters and 100% schema description coverage, so there is nothing for the description to document. The description adds useful context by clarifying that COT values are explicit inputs to the overlay rather than tool parameters the caller must pass to this MCP call.

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 ('Get') and a specific resource ('audited Pine overlay'), and clearly defines what the overlay renders: a supplied COT crowding context plus the chart's prior daily structure range. This differentiates it from siblings like get_cot_crowding_unwind_context, which fetches context, and get_analysis_overlay_template, which is generic.

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 makes the usage context clear: use this when you have a COT crowding context to supply and need the corresponding Pine overlay. It does not explicitly name alternatives or state when not to use it, but the boundary between this tool and data-fetching tools is implied well.

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