get_analysis_overlay_template

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 explicitly states 'Read-only,' which is the most important behavioral trait for this zero-parameter getter. It also clarifies that the returned source is meant for a one-time setup, adding useful lifecycle context beyond a bare 'get template' statement.

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 sentences convey the resource, its content, its read-only nature, and the entire setup workflow without wasted words. The key identifying information is front-loaded, and the follow-up tool references earn their place by preventing misuse.

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 template getter with no output schema, the description is complete: it explains what the tool returns, that it is read-only, and how the returned value should be used across the intended Pine overlay lifecycle. Nothing essential is missing for an agent to invoke it correctly.

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 no parameters and schema description coverage is 100%, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on the return value and downstream usage rather than parameters.

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'), a specific resource ('audited generic Pine overlay'), and the overlay's purpose: rendering a structured market analysis with entry zone, confirmation, invalidation, stop, targets, confidence, and expiry. It clearly distinguishes this tool as the template-getter in the Pine overlay workflow, separate from save_pine_script, add_pine_to_chart, and apply_analysis_overlay.

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 explicitly outlines the intended workflow: pass the returned source to save_pine_script, add_pine_to_chart once, and use apply_analysis_overlay for subsequent analyses. This gives the agent clear when-to-use and when-not-to-use guidance, including the correct alternative for updating existing studies.

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